-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Use a systemd service instead of nohup in advanced deployment documentation #109
Comments
SystemD would make the system require... Well systemD, recently I was thinking about changing the guide to use PM2 instead though which would accomplish the same thing |
Admittedly, using nohup was a quick solution to make it work on my system which at the time was running OpenRC Gentoo, (systemD less) and I didn't know how to make OpenRC services yet |
Whichever works on the most systems. Feel free to change the title of this issue to "use PM2" for tracking purposes. |
I don't see why both/all options can be provided. For ease of use, pm2 (as much as I personally would like to avoid it) is the best choice for the majority reading that docs page. pm2 supports starting itself on boot through an enabled systemd service. Power users can always write their own systemd service with ease. By the way, "systemd", not "systemD". |
Pedantic as ever blu |
LOL true, true. |
Closed as stale |
I suggest making a script that generates a systemd service to run the proxy automatically on startup. This is the more common approach to having a Node server run 24/7.
This issue deals with this page
The text was updated successfully, but these errors were encountered: