4 # Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
5 VAGRANTFILE_API_VERSION = "2"
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.
12 # Every Vagrant virtual environment requires a box to build off of.
13 config.vm.box = "packer/debian64_buster.box"
15 # Disable automatic box update checking. If you disable this, then
16 # boxes will only be checked for updates when the user runs
17 # `vagrant box outdated`. This is not recommended.
18 # config.vm.box_check_update = false
20 # Create a forwarded port mapping which allows access to a specific port
21 # within the machine from a port on the host machine. In the example below,
22 # accessing "localhost:8080" will access port 80 on the guest machine.
23 # config.vm.network "forwarded_port", guest: 80, host: 8080
25 # Create a private network, which allows host-only access to the machine
26 # using a specific IP.
27 # config.vm.network "private_network", ip: "192.168.33.10"
29 # Create a public network, which generally matched to bridged network.
30 # Bridged networks make the machine appear as another physical device on
32 # config.vm.network "public_network"
34 # If true, then any SSH connections made will enable agent forwarding.
35 # Default value: false
36 # config.ssh.forward_agent = true
38 # Share an additional folder to the guest VM. The first argument is
39 # the path on the host to the actual folder. The second argument is
40 # the path on the guest to mount the folder. And the optional third
41 # argument is a set of non-required options.
42 # config.vm.synced_folder "../data", "/vagrant_data"
44 # Provider-specific configuration so you can fine-tune various
45 # backing providers for Vagrant. These expose provider-specific options.
46 # Example for VirtualBox:
48 config.vm.provider "virtualbox" do |vb|
49 # Don't boot with headless mode
52 # Use VBoxManage to customize the VM. For example to change memory:
53 # vb.customize ["modifyvm", :id, "--memory", "1024"]
56 # View the documentation for the provider you're using for more
57 # information on available options.
59 # Enable provisioning with CFEngine. CFEngine Community packages are
60 # automatically installed. For example, configure the host as a
61 # policy server and optionally a policy file to run:
63 # config.vm.provision "cfengine" do |cf|
64 # cf.am_policy_hub = true
65 # # cf.run_file = "motd.cf"
68 # You can also configure and bootstrap a client to an existing
71 # config.vm.provision "cfengine" do |cf|
72 # cf.policy_server_address = "10.0.2.15"
75 # Enable provisioning with Puppet stand alone. Puppet manifests
76 # are contained in a directory path relative to this Vagrantfile.
77 # You will need to create the manifests directory and a manifest in
78 # the file default.pp in the manifests_path directory.
80 # config.vm.provision "puppet" do |puppet|
81 # puppet.manifests_path = "manifests"
82 # puppet.manifest_file = "site.pp"
85 # Enable provisioning with chef solo, specifying a cookbooks path, roles
86 # path, and data_bags path (all relative to this Vagrantfile), and adding
87 # some recipes and/or roles.
89 # config.vm.provision "chef_solo" do |chef|
90 # chef.cookbooks_path = "../my-recipes/cookbooks"
91 # chef.roles_path = "../my-recipes/roles"
92 # chef.data_bags_path = "../my-recipes/data_bags"
93 # chef.add_recipe "mysql"
96 # # You may also specify custom JSON attributes:
97 # chef.json = { :mysql_password => "foo" }
100 # Enable provisioning with chef server, specifying the chef server URL,
101 # and the path to the validation key (relative to this Vagrantfile).
103 # The Opscode Platform uses HTTPS. Substitute your organization for
104 # ORGNAME in the URL and validation key.
106 # If you have your own Chef Server, use the appropriate URL, which may be
107 # HTTP instead of HTTPS depending on your configuration. Also change the
108 # validation key to validation.pem.
110 # config.vm.provision "chef_client" do |chef|
111 # chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
112 # chef.validation_key_path = "ORGNAME-validator.pem"
115 # If you're using the Opscode platform, your validator client is
116 # ORGNAME-validator, replacing ORGNAME with your organization name.
118 # If you have your own Chef Server, the default validation client name is
119 # chef-validator, unless you changed the configuration.
121 # chef.validation_client_name = "ORGNAME-validator"