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

hlx up should restart server if helix-query.yaml was modified #1301

Closed
tripodsan opened this issue Feb 14, 2020 · 1 comment
Closed

hlx up should restart server if helix-query.yaml was modified #1301

tripodsan opened this issue Feb 14, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers released

Comments

@tripodsan
Copy link
Contributor

Is your feature request related to a problem? Please describe.
when a config or source file is modified, hlx up automatically reloads/restarts the server.
this is not the case when helix-query.yaml is modified.

Describe the solution you'd like
automatically restart/reload the simulator, then helix-query.yaml is modified.

@tripodsan tripodsan added enhancement New feature or request good first issue Good for newcomers labels Feb 14, 2020
@trieloff trieloff changed the title hlx up should restart server if index-query.yaml was modified hlx up should restart server if helix-query.yaml was modified Feb 14, 2020
@stefan-guggisberg stefan-guggisberg self-assigned this Feb 18, 2020
trieloff pushed a commit that referenced this issue Feb 18, 2020
# [7.5.0](v7.4.2...v7.5.0) (2020-02-18)

### Features

* **up.cmd.js:** watch helix-query.yaml and restart on modification ([#1307](#1307)) ([0e73a63](0e73a63)), closes [#1301](#1301)
@adobe-bot
Copy link
Collaborator

🎉 This issue has been resolved in version 7.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
Labels
enhancement New feature or request good first issue Good for newcomers released
Projects
None yet
Development

No branches or pull requests

3 participants