Consider using pm2 instead of systemd
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The pm2 process manager is now in use on phet-server2 (and phet-server-dev) by phet-admin. I don't know if it will be helpful for rosetta, but I wanted to make sure the rosetta devs were aware.
I started using pm2 for the new user services to take advantage of the cluster mode, it is now running as a stateless process on N processors instead of a single threaded process, and it was really easy to set that up. I’m not sure if rosetta will ever have enough demand to make that desirable, but there is a good discussion of the differences between the prominent node based process managers and systemd here: https://expressjs.com/en/advanced/pm.html. Definitely not something to be done in a hurry, just something to consider for rosetta 2.1 or 3.0 perhaps.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked Express discussion about Node-based process managers, then compare its pm2 considerations with Rosetta's current systemd setup. The issue does not identify files, tests, or a concrete acceptance condition; a completed effort would first need a decided migration scope for a future Rosetta release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100