Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define different port ranges #37

Open
russellshackleford opened this issue Mar 2, 2023 · 2 comments
Open

Define different port ranges #37

russellshackleford opened this issue Mar 2, 2023 · 2 comments

Comments

@russellshackleford
Copy link

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.

@russellshackleford
Copy link
Author

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.

@russellshackleford
Copy link
Author

I figured out that I could define the port in config/vms.yaml instead of in config/roles.yaml. Not the most ideal, but does solve the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant