You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using oscar-stack for multiple dev environments. If I run plain vagrant up, with the same roles/vms.yaml, I can rely on a consistent spinup order, which means I can rely on a consistent port mapping order and thus can set aliases and config in .ssh/config. This immediately breaks with more than one stack unless every stack is started up in the same order all the time. This hits a wall on system resources, however, if I have a lot of stacks, even if I can power down the unneeded ones after starting them all so that the last one has a predictable port. Obviously if I pass an incomplete list of hosts (or a list sorted differently than vms.yaml) this will also break, but something that allows a bare up to use ports X to Y would minimize the friction considerably.
The text was updated successfully, but these errors were encountered:
or perhaps, putting the port mapping into a file so the same port could be attempted any time that host is later stopped/started? I don't need any sort of special ordering, just a consistent port for any given instance.
I'm using oscar-stack for multiple dev environments. If I run plain
vagrant up
, with the same roles/vms.yaml, I can rely on a consistent spinup order, which means I can rely on a consistent port mapping order and thus can set aliases and config in.ssh/config
. This immediately breaks with more than one stack unless every stack is started up in the same order all the time. This hits a wall on system resources, however, if I have a lot of stacks, even if I can power down the unneeded ones after starting them all so that the last one has a predictable port. Obviously if I pass an incomplete list of hosts (or a list sorted differently than vms.yaml) this will also break, but something that allows a bareup
to use ports X to Y would minimize the friction considerably.The text was updated successfully, but these errors were encountered: