env_XXX in Process File should handle pm2 specific attributes
Open
Nobody has claimed this yet.
SYS: CLI
T: Enhancement
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
Allow to set PM2 attributes in the different env_XXX in Process files
module.exports = {
apps : [{
name : 'HTTP-API',
script : 'http.js',
exec_mode : 'fork',
env_production : {
NODE_ENV : 'production',
max_memory_restart : '260M',
trace : true,
exec_mode : 'cluster',
instances : 4,
}
}]
}
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
No file, test, or entry point is named in the issue. Start by tracing how env_XXX configuration is selected and how PM2 attributes are validated or applied, using the example as the expected input. Done means PM2-specific attributes such as max_memory_restart, trace, exec_mode, and instances work from an env_XXX block.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100