Hi Shawn, you have a few options here, e.g.:
1. Most simple: Vagrant starts the VMs in the order they are defined. You may want to use the `--no-parallel` flag if you are using a provider that supports parallelization (VirtualBox does not) 2. Better: use vagrant-triggers plugin and define and `after :up` command. This does not depend on Vagrants VM ordering and you can create your own checks that go beyond "vm is up", e.g. "webapp is now fully started" HTH, Torben On Sat, Jan 3, 2015 at 6:28 PM, Shawn McCarthy <shawn.mccart...@gmail.com> wrote: > I have a multi-machine Vagrantfile, and I want one box to depend on another > box. So if Box B depends on Box A already being up/started, but Box A is NOT > up/started, and I try to start Box B, I would get an error message or > something. Is this possible with Vagrant ? I couldn't find anything in this > google group or googling in general. > > If not, is it possible with a plugin (I can try and create one if no one > doesn't exist, and other people think it would be possible). > > Thank you! > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to vagrant-up+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
