-
Notifications
You must be signed in to change notification settings - Fork 66
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
Add kill URL to shut down the server? #1939
Labels
Comments
or just:
or
|
Yes, that would be the user-friendly wrapper around that feature. |
trieloff
added a commit
that referenced
this issue
Mar 1, 2022
trieloff
added a commit
that referenced
this issue
Mar 1, 2022
…server instances on the same port fixes #1939
Merged
adobe-bot
pushed a commit
that referenced
this issue
Mar 2, 2022
# [14.5.0](v14.4.28...v14.5.0) (2022-03-02) ### Features * **cli:** add `--kill` option (default: on) to kill other Helix CLI server instances on the same port ([13275e4](13275e4)), closes [#1939](#1939) * **server:** add `/.kill` switch to quickly turn the server off ([af2d458](af2d458)), closes [#1939](#1939)
🎉 This issue has been resolved in version 14.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When working on multiple helix projects at the same time, you will often find out that
hlx up
fails, because port 3000 is already in use. What if, instead of searching for the console tab that has the running process, you could justcurl http://localhost/.kill && hlx up
, which would shut down the existing process, free the port and allow starting the new server without leaving the console?The text was updated successfully, but these errors were encountered: