Skip to content
New issue

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

Allow env vars per each ecosystem's deploy #847

Merged
merged 7 commits into from
Nov 28, 2014
Merged

Allow env vars per each ecosystem's deploy #847

merged 7 commits into from
Nov 28, 2014

Conversation

koresar
Copy link

@koresar koresar commented Nov 27, 2014

Implements Unitech/pm2-deploy#29 ( and #748 )

app.env = app.env || {};

// First merge variables from deploy.production.env object as least priority.
if (deployConf && deployConf[envName] && deployConf[envName]['env']) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

envName should be checked here too, e.g.:

if (envName && deployConf && ...)

@koresar
Copy link
Author

koresar commented Nov 27, 2014

I should have changed docs. What do you guys think?

@soyuka
Copy link
Collaborator

soyuka commented Nov 27, 2014

Docs improvements are always good, if you think that it's missing something feel free to add it ;)

…est is app.env_dev. Update docs. Update sample ecosystem.json when doing `pm2 ecosystem`.
@koresar
Copy link
Author

koresar commented Nov 27, 2014

Docs updates. Feel free to merge or tell me what you think. :)

Unitech added a commit that referenced this pull request Nov 28, 2014
Allow env vars per each ecosystem's deploy
@Unitech Unitech merged commit 677e9b3 into Unitech:development Nov 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants