haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fix opscode platform uri and clarify settings

This commit is contained in:
jtimberman 2010-11-14 10:08:48 -07:00 committed by Mitchell Hashimoto
parent 52023f2fd3
commit cdd1be4be5
1 changed files with 17 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
templates/commands/init/Vagrantfile.erb
View File

@ -40,12 +40,22 @@ Vagrant::Config.run do |config|
# Enable provisioning with chef server, specifying the chef server URL, # Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile). # and the path to the validation key (relative to this Vagrantfile).
# #
# config.vm.provisioner = :chef_server # The Opscode Platform uses HTTPS. Substitute your organization for
# config.chef.chef_server_url = "http://api.opscode.com/organizations/organization" # ORGNAME in the URL and validation key.
# config.chef.validation_key_path = "kiip-validator.pem"
# #
# If you're using the OpsCode platform, you'll have to set this as well. # If you have your own Chef Server, use the appropriate URL, which may be
# If you're using your own chef server, you may have to set it, but it depends # HTTP instead of HTTPS depending on your configuration. Also change the
# on how your Chef server is configured. # validation key to validation.pem.
# config.chef.validation_client_name = "organization-validator" #
# config.vm.provisioner = :chef_server
# config.chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
# config.chef.validation_key_path = "ORGNAME-validator.pem"
#
# 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.
#
# config.chef.validation_client_name = "ORGNAME-validator"
end end