Is it possible to set env specific options (like autorestart) in application declaration file?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
We have some issues with the autorestart feature and would like to set it to false on our development system. On all other environments we'd like the option to be on. Our processes.yml looks like this:
apps:
- script: node
name: app
args:
- build/src/main.js
env_development:
NODE_ENV: development
watch: build
autorestart: false
env_production:
NODE_ENV: production
autorestart: true
The watch option works, but we could only get autorestart to work when putting it on the top level like this:
apps:
- script: node
name: app
autorestart: false
...
Are we using it the wrong way or is there simply no way to control these things on an environment level?
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 with the processes.yml environment configuration shown in the report and trace how the working watch option differs from autorestart. Confirm whether environment-specific autorestart is supported; done means a clear configuration behavior, documentation, or a focused change covering both development and production settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100