How to reload the configuration after starting the configuration update?
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?
How to reload the configuration after starting the configuration update "cwd" field?
ecosystem.config.js:
{
"apps": [
{
"name": "app",
"cwd": "/data/demo",
"instances": 1,
"exec_interpreter": "/bin/node",
"exec_mode": "fork",
"log_date_format": "YYYY-MM-DD HH:mm:ss",
"error_file": "/logs/app-err.log",
"out_file": "/dev/null",
"env": {
"NODE_ENV": "production"
}
}
]
}
When I change the cwd field and run pm2 startOrReload ecosystem.config.js --only app, I run pm2 info app to see that cwd field is not updated.
Now I must delete and restart to update. Is there a more friendly way to reload it?
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
Reproduce the behavior with ecosystem.config.js and pm2 startOrReload ecosystem.config.js --only app, then inspect the result with pm2 info app. Trace how the cwd field is handled during reload. Done means changing cwd and reloading updates the process configuration without deleting and restarting the app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100