Feature request - pm2 resurrect --update-env
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
Currently, pm2 resurrect maintains the environment from time of when it was killed. This is a problem for putting the same image into different environments. The workaround I'm currently using is:
pm2 resurrect; pm2 reload all --update-env
This delays startup and is less than optimal. I would prefer to instead be able to:
pm2 resurrect --update-env
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 tracing the CLI implementation of pm2 resurrect and compare it with the existing pm2 reload all --update-env behavior. Determine where the resurrect command handles options and environment restoration; done means pm2 resurrect --update-env refreshes the environment without requiring a separate reload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100