Debian Codegraph @

release/Vagrantfile

raw
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 = "trustyvm"
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 = "https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.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.168.33.10"
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
42 # Note from <[email protected]>: this does not work well where
43 # the host VirtualBox and the downloaded image disagree on the specific
44 # version of guest tools.
45 # config.vm.synced_folder "..", "/vagrant_data"
46
47 # Provider-specific configuration so you can fine-tune various
48 # backing providers for Vagrant. These expose provider-specific options.
49 # Example for VirtualBox:
50 #
51 # config.vm.provider "virtualbox" do |vb|
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 trustyvm.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
81 # Install the module for handling apt
82 config.vm.provision :shell do |shell|
83 shell.inline = "if [ ! -d /etc/puppet/modules/apt ]; then
84 mkdir -p /etc/puppet/modules;
85 puppet module install puppetlabs/apt;
86 fi"
87 end
88
89 config.vm.provision "puppet" do |puppet|
90 puppet.manifests_path = "manifests"
91 puppet.manifest_file = "trustyvm.pp"
92 end
93
94 # Enable provisioning with chef solo, specifying a cookbooks path, roles
95 # path, and data_bags path (all relative to this Vagrantfile), and adding
96 # some recipes and/or roles.
97 #
98 # config.vm.provision "chef_solo" do |chef|
99 # chef.cookbooks_path = "../my-recipes/cookbooks"
100 # chef.roles_path = "../my-recipes/roles"
101 # chef.data_bags_path = "../my-recipes/data_bags"
102 # chef.add_recipe "mysql"
103 # chef.add_role "web"
104 #
105 # # You may also specify custom JSON attributes:
106 # chef.json = { :mysql_password => "foo" }
107 # end
108
109 # Enable provisioning with chef server, specifying the chef server URL,
110 # and the path to the validation key (relative to this Vagrantfile).
111 #
112 # The Opscode Platform uses HTTPS. Substitute your organization for
113 # ORGNAME in the URL and validation key.
114 #
115 # If you have your own Chef Server, use the appropriate URL, which may be
116 # HTTP instead of HTTPS depending on your configuration. Also change the
117 # validation key to validation.pem.
118 #
119 # config.vm.provision "chef_client" do |chef|
120 # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
121 # chef.validation_key_path = "ORGNAME-validator.pem"
122 # end
123 #
124 # If you're using the Opscode platform, your validator client is
125 # ORGNAME-validator, replacing ORGNAME with your organization name.
126 #
127 # If you have your own Chef Server, the default validation client name is
128 # chef-validator, unless you changed the configuration.
129 #
130 # chef.validation_client_name = "ORGNAME-validator"
131 end