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

[unitctl] Support system filewatcher for restart command #1437

Open
4141done opened this issue Sep 20, 2024 · 0 comments
Open

[unitctl] Support system filewatcher for restart command #1437

4141done opened this issue Sep 20, 2024 · 0 comments
Assignees

Comments

@4141done
Copy link

4141done commented Sep 20, 2024

This is a feature request!

Can unitctl enable an "auto reload" workflow for app development without additional scripting?

When I'm working on a Phoenix application (I'm aware the underlying language is not supported - just giving an example of the experience). Basic flow is:

  1. Start the server mix phx.server
  2. Initial compile and serve
  3. The process lets me know it is watching for changes
  4. Change something in one of the source files
  5. Rebuild, I can now interact with my application and it will reflect the latest changes.

There are some caveats - certain files to require a full restart based on framework minutiae.

Example output:

Compiling 14 files (.ex)
Generated bloopsy app
[info] Running BloopsyWeb.Endpoint with Bandit 1.5.7 at 127.0.0.1:4000 (http)
[info] Access BloopsyWeb.Endpoint at http://localhost:4000
[debug] Downloading esbuild from https://registry.npmjs.org/@esbuild/darwin-arm64/0.17.11

Rebuilding...

Done in 320ms.
[watch] build finished, watching for changes...
# I made a change here
Rebuilding...

Done in 72ms.

It would be cool if I could follow a similar workflow with unitctl where it finds the system filewatcher and watches project files.

@javorszky javorszky self-assigned this Sep 23, 2024
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

2 participants