|
| 1 | +# -*- mode: ruby -*- |
| 2 | +# vi: set ft=ruby : |
| 3 | + |
| 4 | +# All Vagrant configuration is done below. The "2" in Vagrant.configure |
| 5 | +# configures the configuration version (we support older styles for |
| 6 | +# backwards compatibility). Please don't change it unless you know what |
| 7 | +# you're doing. |
| 8 | +Vagrant.configure("2") do |config| |
| 9 | + # The most common configuration options are documented and commented below. |
| 10 | + # For a complete reference, please see the online documentation at |
| 11 | + # https://docs.vagrantup.com. |
| 12 | + |
| 13 | + # Every Vagrant development environment requires a box. You can search for |
| 14 | + # boxes at https://vagrantcloud.com/search. |
| 15 | + config.vm.box = "cilium/docker-registry" |
| 16 | + config.vm.box_version = "0.0.1" |
| 17 | + |
| 18 | + # Disable automatic box update checking. If you disable this, then |
| 19 | + # boxes will only be checked for updates when the user runs |
| 20 | + # `vagrant box outdated`. This is not recommended. |
| 21 | + # config.vm.box_check_update = false |
| 22 | + |
| 23 | + # Create a forwarded port mapping which allows access to a specific port |
| 24 | + # within the machine from a port on the host machine. In the example below, |
| 25 | + # accessing "localhost:8080" will access port 80 on the guest machine. |
| 26 | + # NOTE: This will enable public access to the opened port |
| 27 | + # config.vm.network "forwarded_port", guest: 80, host: 8080 |
| 28 | + |
| 29 | + # Create a forwarded port mapping which allows access to a specific port |
| 30 | + # within the machine from a port on the host machine and only allow access |
| 31 | + # via 127.0.0.1 to disable public access |
| 32 | + # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1" |
| 33 | + |
| 34 | + # Create a private network, which allows host-only access to the machine |
| 35 | + # using a specific IP. |
| 36 | + # config.vm.network "private_network", ip: "192.168.33.10" |
| 37 | + |
| 38 | + # Create a public network, which generally matched to bridged network. |
| 39 | + # Bridged networks make the machine appear as another physical device on |
| 40 | + # your network. |
| 41 | + # config.vm.network "public_network" |
| 42 | + |
| 43 | + # Share an additional folder to the guest VM. The first argument is |
| 44 | + # the path on the host to the actual folder. The second argument is |
| 45 | + # the path on the guest to mount the folder. And the optional third |
| 46 | + # argument is a set of non-required options. |
| 47 | + # config.vm.synced_folder "../data", "/vagrant_data" |
| 48 | + |
| 49 | + # Provider-specific configuration so you can fine-tune various |
| 50 | + # backing providers for Vagrant. These expose provider-specific options. |
| 51 | + # Example for VirtualBox: |
| 52 | + # |
| 53 | + # config.vm.provider "virtualbox" do |vb| |
| 54 | + # # Display the VirtualBox GUI when booting the machine |
| 55 | + # vb.gui = true |
| 56 | + # |
| 57 | + # # Customize the amount of memory on the VM: |
| 58 | + # vb.memory = "1024" |
| 59 | + # end |
| 60 | + # |
| 61 | + # View the documentation for the provider you are using for more |
| 62 | + # information on available options. |
| 63 | + |
| 64 | + # Enable provisioning with a shell script. Additional provisioners such as |
| 65 | + # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the |
| 66 | + # documentation for more information about their specific syntax and use. |
| 67 | + # config.vm.provision "shell", inline: <<-SHELL |
| 68 | + # apt-get update |
| 69 | + # apt-get install -y apache2 |
| 70 | + # SHELL |
| 71 | +end |
0 commit comments