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

Support for autostarting using systemd socket activation #101

Open
jonnor opened this issue Dec 13, 2016 · 1 comment
Open

Support for autostarting using systemd socket activation #101

jonnor opened this issue Dec 13, 2016 · 1 comment

Comments

@jonnor
Copy link
Member

jonnor commented Dec 13, 2016

One generally has several projects made with NoFlo. And when switching between them in Flowhub, one needs to set up the corresponding runtime (usually node-nodejs) in the right directory, before one can connect to it.
However, with systemd socket activation a service can be started (and then stopped after a time) when traffic comes in on a port, for instance from Flowhub.
http://0pointer.de/blog/projects/socket-activation.html

systemd provides some C APIs for this, accessible for instance via https://github.com/rubenv/node-systemd
However, it sounds like that may not be neccesary, as systemd also sets LISTEN_FDS envvar, and then file descriptor 3 is the one to use. rubenv/node-systemd#12 (comment)

@jonnor
Copy link
Member Author

jonnor commented Dec 13, 2016

Might also want a systemd .service unit generator, like msgflo/msgflo#20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant