We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I wish I could avoid "env_staging": { "NODE_ENV": "staging" } lines in each of my (dozens) of microservices.
"env_staging": { "NODE_ENV": "staging" }
{ "apps": [ { "name": "app1", "script": ".", "env_staging": { "NODE_ENV": "staging" } }, { "name": "app2", "instances": "1", "env_staging": { "NODE_ENV": "staging" } } ], "deploy": { "staging": { "user": "username", "host": "192.168.0.52", "ref": "origin/staging", "repo": "repo@url.git", "path": "/home/username", "post-deploy": "npm install && (pm2 stop all; gulp && pm2 startOrRestart ecosystem.json --env staging)" } }
Can we have default ENV variables per each deploy record to avoid repetitiveness? Like:
{ "deploy": { "staging": { // ... "env": { "NODE_ENV": "staging" } // ... } }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I wish I could avoid
"env_staging": { "NODE_ENV": "staging" }
lines in each of my (dozens) of microservices.Can we have default ENV variables per each deploy record to avoid repetitiveness? Like:
The text was updated successfully, but these errors were encountered: