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
[cli / main] Support allocating ports at via run command #251
[cli / main] Support allocating ports at via run command #251
Conversation
Sorry, needed to split this out of my master branch so I can push out a few additional changes. See #250 for related discussion. |
-P seems like a reasonable change to avoid confusion. A -p would definitely be nice, but I'm not going to pursue that for now in this branch. I'll add tests too, though I'm not actually able to get the test suite to pass - is there something more I need to do other than: $ virtualenv venv
$ source venv/bin/active
$ pip install -r requirements.txt
$ pip install -r requirements-dev.txt
$ script/test (I'll report back with test results when it finishes - it seems to take well over an hour to complete the test suite running the above set of commands.) |
Here's my test run output for the commands above:
|
Looks like port conflicts. Do you have anything else running, in Docker or otherwise? |
Thanks for this, Philip! This looks really great. What version of Docker are you running? You need Docker 0.11 or 1.0.0. |
Whoops, it was some other services eating ports combined with the test suite assuming the containing folder is named |
D'oh. Sorry about that. #45's fault I guess. |
Hey @philipkimmey this looks awesome thanks, but we really need the tests before we can merge it. Are you still interested in adding the tests and getting this merged? |
Should be |
It's been a long while and this seems to have good support – any news on getting this in? Can I help somehow? |
Almost there! 3 things:
|
Yeah I'm sorry guys, haven't had a chance to return to this one - I'll attempt to pick it back up this weekend though I'm not sure if I'll get to it realistically. |
Another thing worth thinking about is how this relates to the |
#485 looks more robust for sure - looking forward to that making it into master! |
This needs a mention on http://www.fig.sh/cli.html |
No description provided.