-
Notifications
You must be signed in to change notification settings - Fork 339
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 background processes #83
Conversation
This is first and foremost a PoC, so feel free to voice any concerns you might have, I'm more than happy to address them :) |
Use `devenv up -d` to run honcho processes in the background with nohup. `devenv down` and `devenv logs` are also included. See cachix#80.
29c117a
to
864f1fe
Compare
I'm still not sure about this one. Could you explain what kind of workflow do you have that requires this interface? |
I often do not need to see application logs while working on the app, so I find it kinda annoying that I need to keep one terminal running just to keep the app running. |
I would like to call that also in Gitpod to have one shell. devenv up -d and let the user work in the shell and don't have to care about the running services |
We need to figure how how this interacts with different process backends. Probably each needs to return a pid? |
I guess so, yes |
I recommend creating a prototype using https://github.com/NixOS/nixpkgs/blob/e66309ddcce8fc316b9addeabd11bf2187fa2eb9/pkgs/tools/system/daemonize/default.nix. |
Started discussion about upstreaming this feature to This way not only the honcho implementation could fulfill the new interface. |
e82dccf
to
2cae5ec
Compare
Another use case is bootstrapping the project. |
This is now implemented in #745 |
Use
devenv up -d
to run honcho withnohup
.devenv down
anddevenv logs
are also included and are analog to theirdocker-compose
counterparts.