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

Remove forever and start-stop-daemon deps => try nodemon and pm2 instead #151

Closed
adrienjoly opened this issue Aug 15, 2018 · 1 comment
Closed

Comments

@adrienjoly
Copy link
Member

adrienjoly commented Aug 15, 2018

  • try https://nodemon.io/ on dev environment (watch changes->restart)
  • try pm2 to run in production

=> get rid of start-stop-daemon, forever, and their dependancies


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@adrienjoly adrienjoly self-assigned this May 1, 2021
@adrienjoly adrienjoly added this to 📥 Inbox / ideas in Development via automation May 1, 2021
@adrienjoly adrienjoly moved this from 📥 Inbox / ideas to 🌲 In production in Development May 1, 2021
adrienjoly pushed a commit that referenced this issue May 1, 2021
## [1.44.35](v1.44.34...v1.44.35) (2021-05-01)

### Bug Fixes

* **prod:** Switch from forever to PM2 ([e34c535](e34c535)), closes [#151](#151)
@adrienjoly
Copy link
Member Author

Note: We now use pm2 reload to restart openwhyd server in production, but 0-downtime deploy is not possible yet because we have not enabled the cluster mode yet, because openwhyd's server is not stateless yet. Cf https://pm2.keymetrics.io/docs/usage/cluster-mode/#reload

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

No branches or pull requests

1 participant