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