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

server restart doesn't work if using auto port selection #148

Closed
joelanman opened this issue Feb 12, 2016 · 4 comments
Closed

server restart doesn't work if using auto port selection #148

joelanman opened this issue Feb 12, 2016 · 4 comments
Labels
🐛 Bug Something isn't working the way it should (including incorrect wording in documentation)

Comments

@joelanman
Copy link
Contributor

steps to reproduce:

  1. start prototype A (it defaults to port 3000)
  2. start prototype B
  3. answer yes to suggested port (3001)
  4. make a change to routes.js

prototype B will now restart, but it will stop because port 3000 is still in use by prototype A. If you try and refresh the browser, prototype B won't be running any more, until you answer 'yes' again in the terminal

@joelanman joelanman added the 🐛 Bug Something isn't working the way it should (including incorrect wording in documentation) label Feb 12, 2016
@edwardhorsford
Copy link
Contributor

curses!

@edwardhorsford
Copy link
Contributor

Not really sure how to address this. Suggestions?

@joelanman
Copy link
Contributor Author

Store the port in a file, then try and read from it when starting up. On Ctrl c delete it

joelanman added a commit that referenced this issue Feb 18, 2016
joelanman added a commit that referenced this issue Feb 18, 2016
@joelanman
Copy link
Contributor Author

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Something isn't working the way it should (including incorrect wording in documentation)
Projects
None yet
Development

No branches or pull requests

2 participants