Consider setting pm2-logroate on by default
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
I've repeatedly run out of memory on my local server, enough that it's become a bit irritating. I eventually set up some hacky reminders to run pm2 flush, but decided to look into this properly, and found that pm2-logrotate solves this problem completely. Maybe consider setting it on by default with some sensible parameters? Alternatively, consider setting a more prominent reminder in the README that pm2 can end up filling your whole memory.
I'm hugely appreciative of pm2 in general, but I thought I'd report on this.
Contributor guide
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
Review the pm2-logrotate behavior and the README guidance around pm2 flush and log growth. First determine whether the intended outcome is enabling rotation by default or improving the README warning; done should be a decided, documented behavior with suitable parameters or a clear reminder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100