|
| 1 | +# -*- mode: ruby -*- |
| 2 | +# vi: set ft=ruby : |
| 3 | + |
| 4 | +# Vagrantfile API/syntax version. Don't touch unless you know what you're doing! |
| 5 | +VAGRANTFILE_API_VERSION = "2" |
| 6 | + |
| 7 | +Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| |
| 8 | + # All Vagrant configuration is done here. The most common configuration |
| 9 | + # options are documented and commented below. For a complete reference, |
| 10 | + # please see the online documentation at vagrantup.com. |
| 11 | + |
| 12 | + # Every Vagrant virtual environment requires a box to build off of. |
| 13 | + config.vm.box = "hashicorp/precise64" |
| 14 | + |
| 15 | + # The url from where the 'config.vm.box' box will be fetched if it |
| 16 | + # doesn't already exist on the user's system. |
| 17 | + # config.vm.box_url = "http://domain.com/path/to/above.box" |
| 18 | + |
| 19 | + # Create a forwarded port mapping which allows access to a specific port |
| 20 | + # within the machine from a port on the host machine. In the example below, |
| 21 | + # accessing "localhost:8080" will access port 80 on the guest machine. |
| 22 | + # config.vm.network "forwarded_port", guest: 80, host: 8080 |
| 23 | + |
| 24 | + # Create a private network, which allows host-only access to the machine |
| 25 | + # using a specific IP. |
| 26 | + config.vm.network "private_network", ip: "192.2.2.2" |
| 27 | + |
| 28 | + # Create a public network, which generally matched to bridged network. |
| 29 | + # Bridged networks make the machine appear as another physical device on |
| 30 | + # your network. |
| 31 | + # config.vm.network "public_network" |
| 32 | + |
| 33 | + # If true, then any SSH connections made will enable agent forwarding. |
| 34 | + # Default value: false |
| 35 | + # config.ssh.forward_agent = true |
| 36 | + |
| 37 | + # Share an additional folder to the guest VM. The first argument is |
| 38 | + # the path on the host to the actual folder. The second argument is |
| 39 | + # the path on the guest to mount the folder. And the optional third |
| 40 | + # argument is a set of non-required options. |
| 41 | + config.vm.synced_folder "./data", "/data" |
| 42 | + |
| 43 | + # Provider-specific configuration so you can fine-tune various |
| 44 | + # backing providers for Vagrant. These expose provider-specific options. |
| 45 | + # Example for VirtualBox: |
| 46 | + # |
| 47 | + config.vm.provider "virtualbox" do |vb| |
| 48 | + # Don't boot with headless mode |
| 49 | + # vb.gui = true |
| 50 | + |
| 51 | + # Use VBoxManage to customize the VM. For example to change memory: |
| 52 | + vb.customize ["modifyvm", :id, "--memory", "4096"] |
| 53 | + end |
| 54 | + # |
| 55 | + # View the documentation for the provider you're using for more |
| 56 | + # information on available options. |
| 57 | + |
| 58 | + # Enable provisioning with Puppet stand alone. Puppet manifests |
| 59 | + # are contained in a directory path relative to this Vagrantfile. |
| 60 | + # You will need to create the manifests directory and a manifest in |
| 61 | + # the file hashicorp/precise64.pp in the manifests_path directory. |
| 62 | + # |
| 63 | + # An example Puppet manifest to provision the message of the day: |
| 64 | + # |
| 65 | + # # group { "puppet": |
| 66 | + # # ensure => "present", |
| 67 | + # # } |
| 68 | + # # |
| 69 | + # # File { owner => 0, group => 0, mode => 0644 } |
| 70 | + # # |
| 71 | + # # file { '/etc/motd': |
| 72 | + # # content => "Welcome to your Vagrant-built virtual machine! |
| 73 | + # # Managed by Puppet.\n" |
| 74 | + # # } |
| 75 | + # |
| 76 | + # config.vm.provision "puppet" do |puppet| |
| 77 | + # puppet.manifests_path = "manifests" |
| 78 | + # puppet.manifest_file = "site.pp" |
| 79 | + # end |
| 80 | + |
| 81 | + # Enable provisioning with chef solo, specifying a cookbooks path, roles |
| 82 | + # path, and data_bags path (all relative to this Vagrantfile), and adding |
| 83 | + # some recipes and/or roles. |
| 84 | + # |
| 85 | + # config.vm.provision "chef_solo" do |chef| |
| 86 | + # chef.cookbooks_path = "../my-recipes/cookbooks" |
| 87 | + # chef.roles_path = "../my-recipes/roles" |
| 88 | + # chef.data_bags_path = "../my-recipes/data_bags" |
| 89 | + # chef.add_recipe "mysql" |
| 90 | + # chef.add_role "web" |
| 91 | + # |
| 92 | + # # You may also specify custom JSON attributes: |
| 93 | + # chef.json = { :mysql_password => "foo" } |
| 94 | + # end |
| 95 | + |
| 96 | + # Enable provisioning with chef server, specifying the chef server URL, |
| 97 | + # and the path to the validation key (relative to this Vagrantfile). |
| 98 | + # |
| 99 | + # The Opscode Platform uses HTTPS. Substitute your organization for |
| 100 | + # ORGNAME in the URL and validation key. |
| 101 | + # |
| 102 | + # If you have your own Chef Server, use the appropriate URL, which may be |
| 103 | + # HTTP instead of HTTPS depending on your configuration. Also change the |
| 104 | + # validation key to validation.pem. |
| 105 | + # |
| 106 | + # config.vm.provision "chef_client" do |chef| |
| 107 | + # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME" |
| 108 | + # chef.validation_key_path = "ORGNAME-validator.pem" |
| 109 | + # end |
| 110 | + # |
| 111 | + # If you're using the Opscode platform, your validator client is |
| 112 | + # ORGNAME-validator, replacing ORGNAME with your organization name. |
| 113 | + # |
| 114 | + # If you have your own Chef Server, the default validation client name is |
| 115 | + # chef-validator, unless you changed the configuration. |
| 116 | + # |
| 117 | + # chef.validation_client_name = "ORGNAME-validator" |
| 118 | +end |
0 commit comments