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

Discussion : Migrate to PM2 #94

Open
YashKumarVerma opened this issue Apr 12, 2021 · 3 comments
Open

Discussion : Migrate to PM2 #94

YashKumarVerma opened this issue Apr 12, 2021 · 3 comments

Comments

@YashKumarVerma
Copy link
Contributor

Is your feature request related to a problem? Please describe.

  • the code currently relies on throng,
  • throng handles a subset of features that are provided by other alternatives like pm2
  • and most importantly, requires a particular application structure and code refactor to work like this function

New Possibilities that open up

  • use a watch mode to test changes in realtime
  • completely isolate application logic and cluster configurations
  • dump logs to file
@birm
Copy link
Member

birm commented Apr 12, 2021

I'm not 100% sold, but watching configs could be a good addition. It's got to be better than nodemon, right? :)

@YashKumarVerma
Copy link
Contributor Author

YashKumarVerma commented Apr 13, 2021

yeah nodemon could definitely handle the live update part, and since nodemon supports a custom config file, we can properly document the configs too. I personally use nodemon for live changes in my projects.

The reason why I wanted to discuss pm2 is that it could perform the actions of both, throng and nodemon, with zero affect on the codebase, plus the benefits that pm2 provides.

@birm
Copy link
Member

birm commented Apr 13, 2021

That's fair. So long as it's not too big/slow on install, I see no issue. :)

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