Suggestion: `pm2 ecosystem` should not overwrite existing ecosystem.config.js
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
Accidentally ran pm2 ecosystem.
How could we reproduce this issue?
- Run
pm2 ecosystem - Edit the file.
- Run
pm2 ecosystem - Thank god you had a backup?
Related: #4094
Code in question is here: https://github.com/Unitech/pm2/blob/a6a52dca0a51aef8332a7bdee444ceeea06a4f0c/lib/API/Extra.js#L642
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
Start by reading lib/API/Extra.js around line 642 and reproduce the behavior with pm2 ecosystem, editing ecosystem.config.js between runs. Compare the behavior with related issue #4094; done means rerunning the command no longer overwrites an existing ecosystem.config.js.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100