33f5e2ed82
This commit should provide enough example information to get started provisioning a box using the Puppet provisioner. The goal of this commit is to provide just enough information to quickly get started but not so much that the configuration file is polluted or confuses the user.
83 lines
3.3 KiB
Plaintext
83 lines
3.3 KiB
Plaintext
Vagrant::Config.run do |config|
|
|
# All Vagrant configuration is done here. The most common configuration
|
|
# options are documented and commented below. For a complete reference,
|
|
# please see the online documentation at vagrantup.com.
|
|
|
|
# Every Vagrant virtual environment requires a box to build off of.
|
|
config.vm.box = "<%= box_name %>"
|
|
|
|
# The url from where the 'config.vm.box' box will be fetched if it
|
|
# doesn't already exist on the user's system.
|
|
<% if box_url.nil? %># <% end %>config.vm.box_url = "<%= box_url || "http://domain.com/path/to/above.box" %>"
|
|
|
|
# Boot with a GUI so you can see the screen. (Default is headless)
|
|
# config.vm.boot_mode = :gui
|
|
|
|
# Assign this VM to a host only network IP, allowing you to access it
|
|
# via the IP.
|
|
# config.vm.network "33.33.33.10"
|
|
|
|
# Forward a port from the guest to the host, which allows for outside
|
|
# computers to access the VM, whereas host only networking does not.
|
|
# config.vm.forward_port "http", 80, 8080
|
|
|
|
# Share an additional folder to the guest VM. The first argument is
|
|
# an identifier, the second is the path on the guest to mount the
|
|
# folder, and the third is the path on the host to the actual folder.
|
|
# config.vm.share_folder "v-data", "/vagrant_data", "../data"
|
|
|
|
# Enable provisioning with Puppet stand alone. Puppet manifests
|
|
# are contained in a directory path relative to this Vagrantfile.
|
|
# You will need to create the manifests directory and a manifest in
|
|
# the file <%= box_name %>.pp in the manifests_path directory.
|
|
#
|
|
# An example Puppet manifest to provision the message of the day:
|
|
#
|
|
# # File { owner => 0, group => 0, mode => 0644 }
|
|
# #
|
|
# # file { '/etc/motd':
|
|
# # content => "Welcome to your Vagrant-built virtual machine!
|
|
# # Managed by Puppet.\n"
|
|
# # }
|
|
#
|
|
# config.vm.provision :puppet do |puppet|
|
|
# puppet.manifests_path = "manifests"
|
|
# puppet.manifest_file = "<%= box_name %>.pp"
|
|
# end
|
|
|
|
# Enable provisioning with chef solo, specifying a cookbooks path (relative
|
|
# to this Vagrantfile), and adding some recipes and/or roles.
|
|
#
|
|
# config.vm.provision :chef_solo do |chef|
|
|
# chef.cookbooks_path = "cookbooks"
|
|
# chef.add_recipe "mysql"
|
|
# chef.add_role "web"
|
|
#
|
|
# # You may also specify custom JSON attributes:
|
|
# chef.json.merge!({ :mysql_password => "foo" })
|
|
# end
|
|
|
|
# Enable provisioning with chef server, specifying the chef server URL,
|
|
# and the path to the validation key (relative to this Vagrantfile).
|
|
#
|
|
# The Opscode Platform uses HTTPS. Substitute your organization for
|
|
# ORGNAME in the URL and validation key.
|
|
#
|
|
# If you have your own Chef Server, use the appropriate URL, which may be
|
|
# HTTP instead of HTTPS depending on your configuration. Also change the
|
|
# validation key to validation.pem.
|
|
#
|
|
# config.vm.provision :chef_server do |chef|
|
|
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
|
|
# chef.validation_key_path = "ORGNAME-validator.pem"
|
|
# end
|
|
#
|
|
# If you're using the Opscode platform, your validator client is
|
|
# ORGNAME-validator, replacing ORGNAME with your organization name.
|
|
#
|
|
# IF you have your own Chef Server, the default validation client name is
|
|
# chef-validator, unless you changed the configuration.
|
|
#
|
|
# chef.validation_client_name = "ORGNAME-validator"
|
|
end
|