Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Initial Vagrantfile

  • Loading branch information...
commit 04371a7e5f3c571fd5e482f34a84e77168350693 1 parent 574fa7a
Joshua Clayton authored

Showing 1 changed file with 96 additions and 0 deletions. Show diff stats Hide diff stats

  1. +96 0 Vagrantfile
96 Vagrantfile
... ... @@ -0,0 +1,96 @@
  1 +# -*- mode: ruby -*-
  2 +# vi: set ft=ruby :
  3 +
  4 +Vagrant::Config.run do |config|
  5 + # All Vagrant configuration is done here. The most common configuration
  6 + # options are documented and commented below. For a complete reference,
  7 + # please see the online documentation at vagrantup.com.
  8 +
  9 + # Every Vagrant virtual environment requires a box to build off of.
  10 + config.vm.box = "base"
  11 +
  12 + # The url from where the 'config.vm.box' box will be fetched if it
  13 + # doesn't already exist on the user's system.
  14 + # config.vm.box_url = "http://domain.com/path/to/above.box"
  15 +
  16 + # Boot with a GUI so you can see the screen. (Default is headless)
  17 + # config.vm.boot_mode = :gui
  18 +
  19 + # Assign this VM to a host-only network IP, allowing you to access it
  20 + # via the IP. Host-only networks can talk to the host machine as well as
  21 + # any other machines on the same network, but cannot be accessed (through this
  22 + # network interface) by any external networks.
  23 + # config.vm.network :hostonly, "33.33.33.10"
  24 +
  25 + # Assign this VM to a bridged network, allowing you to connect directly to a
  26 + # network using the host's network device. This makes the VM appear as another
  27 + # physical device on your network.
  28 + # config.vm.network :bridged
  29 +
  30 + # Forward a port from the guest to the host, which allows for outside
  31 + # computers to access the VM, whereas host only networking does not.
  32 + # config.vm.forward_port 80, 8080
  33 +
  34 + # Share an additional folder to the guest VM. The first argument is
  35 + # an identifier, the second is the path on the guest to mount the
  36 + # folder, and the third is the path on the host to the actual folder.
  37 + # config.vm.share_folder "v-data", "/vagrant_data", "../data"
  38 +
  39 + # Enable provisioning with Puppet stand alone. Puppet manifests
  40 + # are contained in a directory path relative to this Vagrantfile.
  41 + # You will need to create the manifests directory and a manifest in
  42 + # the file base.pp in the manifests_path directory.
  43 + #
  44 + # An example Puppet manifest to provision the message of the day:
  45 + #
  46 + # # group { "puppet":
  47 + # # ensure => "present",
  48 + # # }
  49 + # #
  50 + # # File { owner => 0, group => 0, mode => 0644 }
  51 + # #
  52 + # # file { '/etc/motd':
  53 + # # content => "Welcome to your Vagrant-built virtual machine!
  54 + # # Managed by Puppet.\n"
  55 + # # }
  56 + #
  57 + # config.vm.provision :puppet do |puppet|
  58 + # puppet.manifests_path = "manifests"
  59 + # puppet.manifest_file = "base.pp"
  60 + # end
  61 +
  62 + # Enable provisioning with chef solo, specifying a cookbooks path (relative
  63 + # to this Vagrantfile), and adding some recipes and/or roles.
  64 + #
  65 + # config.vm.provision :chef_solo do |chef|
  66 + # chef.cookbooks_path = "cookbooks"
  67 + # chef.add_recipe "mysql"
  68 + # chef.add_role "web"
  69 + #
  70 + # # You may also specify custom JSON attributes:
  71 + # chef.json = { :mysql_password => "foo" }
  72 + # end
  73 +
  74 + # Enable provisioning with chef server, specifying the chef server URL,
  75 + # and the path to the validation key (relative to this Vagrantfile).
  76 + #
  77 + # The Opscode Platform uses HTTPS. Substitute your organization for
  78 + # ORGNAME in the URL and validation key.
  79 + #
  80 + # If you have your own Chef Server, use the appropriate URL, which may be
  81 + # HTTP instead of HTTPS depending on your configuration. Also change the
  82 + # validation key to validation.pem.
  83 + #
  84 + # config.vm.provision :chef_client do |chef|
  85 + # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
  86 + # chef.validation_key_path = "ORGNAME-validator.pem"
  87 + # end
  88 + #
  89 + # If you're using the Opscode platform, your validator client is
  90 + # ORGNAME-validator, replacing ORGNAME with your organization name.
  91 + #
  92 + # IF you have your own Chef Server, the default validation client name is
  93 + # chef-validator, unless you changed the configuration.
  94 + #
  95 + # chef.validation_client_name = "ORGNAME-validator"
  96 +end

0 comments on commit 04371a7

Please sign in to comment.
Something went wrong with that request. Please try again.