|
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 = "wheezy-73-x64" |
|
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://puppet-vagrant-boxes.puppetlabs.com/debian-73-x64-virtualbox-puppet.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: "172.16.1.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 "../", "/srv/comt" |
|
42 |
|
43 config.vm.define :coment_dev do |coment_dev| |
|
44 end |
|
45 |
|
46 # Provider-specific configuration so you can fine-tune various |
|
47 # backing providers for Vagrant. These expose provider-specific options. |
|
48 # Example for VirtualBox: |
|
49 # |
|
50 config.vm.provider :virtualbox do |vb| |
|
51 vb.name = "coment_dev" |
|
52 # # Don't boot with headless mode |
|
53 # vb.gui = true |
|
54 # |
|
55 # # Use VBoxManage to customize the VM. For example to change memory: |
|
56 # vb.customize ["modifyvm", :id, "--memory", "1024"] |
|
57 end |
|
58 # |
|
59 # View the documentation for the provider you're using for more |
|
60 # information on available options. |
|
61 |
|
62 # Enable provisioning with Puppet stand alone. Puppet manifests |
|
63 # are contained in a directory path relative to this Vagrantfile. |
|
64 # You will need to create the manifests directory and a manifest in |
|
65 # the file base.pp in the manifests_path directory. |
|
66 # |
|
67 # An example Puppet manifest to provision the message of the day: |
|
68 # |
|
69 # # group { "puppet": |
|
70 # # ensure => "present", |
|
71 # # } |
|
72 # # |
|
73 # # File { owner => 0, group => 0, mode => 0644 } |
|
74 # # |
|
75 # # file { '/etc/motd': |
|
76 # # content => "Welcome to your Vagrant-built virtual machine! |
|
77 # # Managed by Puppet.\n" |
|
78 # # } |
|
79 # |
|
80 config.vm.provision :puppet do |puppet| |
|
81 puppet.manifests_path = "manifests" |
|
82 puppet.manifest_file = "site.pp" |
|
83 puppet.module_path = "modules" |
|
84 puppet.options = "--hiera_config /vagrant/hiera.yaml " |
|
85 end |
|
86 |
|
87 # Enable provisioning with chef solo, specifying a cookbooks path, roles |
|
88 # path, and data_bags path (all relative to this Vagrantfile), and adding |
|
89 # some recipes and/or roles. |
|
90 # |
|
91 # config.vm.provision :chef_solo do |chef| |
|
92 # chef.cookbooks_path = "../my-recipes/cookbooks" |
|
93 # chef.roles_path = "../my-recipes/roles" |
|
94 # chef.data_bags_path = "../my-recipes/data_bags" |
|
95 # chef.add_recipe "mysql" |
|
96 # chef.add_role "web" |
|
97 # |
|
98 # # You may also specify custom JSON attributes: |
|
99 # chef.json = { :mysql_password => "foo" } |
|
100 # end |
|
101 |
|
102 # Enable provisioning with chef server, specifying the chef server URL, |
|
103 # and the path to the validation key (relative to this Vagrantfile). |
|
104 # |
|
105 # The Opscode Platform uses HTTPS. Substitute your organization for |
|
106 # ORGNAME in the URL and validation key. |
|
107 # |
|
108 # If you have your own Chef Server, use the appropriate URL, which may be |
|
109 # HTTP instead of HTTPS depending on your configuration. Also change the |
|
110 # validation key to validation.pem. |
|
111 # |
|
112 # config.vm.provision :chef_client do |chef| |
|
113 # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME" |
|
114 # chef.validation_key_path = "ORGNAME-validator.pem" |
|
115 # end |
|
116 # |
|
117 # If you're using the Opscode platform, your validator client is |
|
118 # ORGNAME-validator, replacing ORGNAME with your organization name. |
|
119 # |
|
120 # If you have your own Chef Server, the default validation client name is |
|
121 # chef-validator, unless you changed the configuration. |
|
122 # |
|
123 # chef.validation_client_name = "ORGNAME-validator" |
|
124 end |