Last modified: 2014-07-10 17:08:53 UTC
Right now, running multiple vagrant boxes is somewhat inconvenient: - the IP needs to be changed, and for that, the config.vm.network command in the Vagrantfile needs to be modified/commented out (it has no id, so it cannot be manipulated from another file; when left in place, vagrant will not run because of the conflict) - FORWARDED_PORT cannot be overwritten. This is not that much or a problem, since the actual port definition has an id, but still not nice (Facter will have the wrong port, maybe that will cause issues at some point) - $wgServer has the wrong port number. Again, not a big problem, but it would be nice if it could be managed automatically. - would be nice to have examples in the sample Vagrantfile-extra.rb on how to change all that (plus the ssh port)
(In reply to Tisza Gergő from comment #0) > Right now, running multiple vagrant boxes is somewhat inconvenient: > - the IP needs to be changed, and for that, the config.vm.network command in > the Vagrantfile needs to be modified/commented out (it has no id, so it > cannot be manipulated from another file; when left in place, vagrant will > not run because of the conflict) Can now be set in .settings.yaml using the `static_ip` key. > - FORWARDED_PORT cannot be overwritten. This is not that much or a problem, > since the actual port definition has an id, but still not nice (Facter will > have the wrong port, maybe that will cause issues at some point) Can now be set in .settings.yaml using the `http_port` key. > - $wgServer has the wrong port number. Again, not a big problem, but it > would be nice if it could be managed automatically. This should be handled properly now with the use of the `forwarded_port` factor fact. > - would be nice to have examples in the sample Vagrantfile-extra.rb on how > to change all that (plus the ssh port) Once I7486551 lands `vagrant help config` will provide documentation of the settings and `vagrant config` will be able to manage them.
