Updates prependEnv() to use PM2_ variables.#194
Open
mattdeluco wants to merge 1 commit intoUnitech:masterfrom
Open
Updates prependEnv() to use PM2_ variables.#194mattdeluco wants to merge 1 commit intoUnitech:masterfrom
mattdeluco wants to merge 1 commit intoUnitech:masterfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is my proposed resolution to Issue #37.
A routine has been added to prependEnv() to filter from the process
environment any variable beggining with "PM2_" and add them to the rest
of the environment variables.
Note that the prefix of "PM2_" is truncated from the variable name when applied to the environment of the application.
For example:
$ PM2_AUTHTOKEN=setecastronomy pm2 deploy ecosystem.config.js productionwould set the environment variableAUTHTOKENwhen running the application, available in Node asprocess.env.AUTHTOKEN.