Vagrant::MultiHostsUpdater

This plugin adds an entry to your /etc/hosts file on the host system.

On up, resume and reload commands, it tries to add the information, if it doesn't exist in your hosts file. If it needs to be added, you may be asked for an administrator password, as it requires root privileges to modify it.

On halt and destroy, those entries will be removed again.

$ vagrant plugin install vagrant-multi-hostsupdater

Uninstall it with:

$ vagrant plugin uninstall vagrant-multi-hostsupdater

At the moment, the only things you need, are the hostname and a :private_network network with a fixed ip.

config.vm.network :private_network, ip: "192.168.3.10"
config.vm.hostname = "www.testing.de"
config.multihostsupdater.aliases = ["alias.testing.de", "alias2.somedomain.com"]

If you have multiple network adapters i.e.:

devel.vm.network "private_network", ip: 10.0.0.1
devel.vm.network "private_network", ip: 10.0.0.2

you can specify which hostnames are bound to which IP by passing a Map[String]Array mapping the IP of the network to an array of hostnames to create. eg:

config.multihostsupdater.aliases = {'10.0.0.1' => ['foo.com', 'bar.com'], '10.0.0.2' => ['baz.com', 'bat.com']}

This will produce host entries like so:

10.0.0.1 foo.com
10.0.0.1 bar.com
10.0.0.2 baz.com
10.0.0.2 bat.com

There are some situations in which you don't want Virtualbox to handle multiple private network interfaces. For instance, this is the case of vpn interfaces (like Openvpn tun interfaces).

In these cases you can use the config.multihostsupdater.force_ips setting in this way:

config.multihostsupdater.force_ips = ['10.0.0.1','10.0.0.2']

By setting the remove_on_suspend option, you can have them removed on suspend, too:

config.multihostsupdater.remove_on_suspend = true

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request