Limiting pm2 env to display environment
I've a node.js application running with some environment variables such as secret_keys, database name etc. All variables are set using export command before starting the server.
I'm using 'pm2' tool to start the server. When I use command 'pm2 env ', it displays all the environment correctly but my question is how to prevent display/showing of few variables such as secret keys, etc.
node.js pm2
asked Nov 15 '18 at 5:10
AtarangAtarang
227416
add a comment |
I've a node.js application running with some environment variables such as secret_keys, database name etc. All variables are set using export command before starting the server.
I'm using 'pm2' tool to start the server. When I use command 'pm2 env ', it displays all the environment correctly but my question is how to prevent display/showing of few variables such as secret keys, etc.
node.js pm2
asked Nov 15 '18 at 5:10
AtarangAtarang
227416
did you have any configuration for pm2 or pass environment as command line
– front_end_dev
Nov 15 '18 at 6:50
No configuration but just following few variables, export USER_PASSWORD="xxxxxxxx"; pm2 start server.js
– Atarang
Nov 15 '18 at 9:15
You can manage this using custom configuration of pm2. Read more about from pm2.io/doc/en/runtime/guide/ecosystem-file/…
– front_end_dev
Nov 15 '18 at 11:48
Setting environment is okay. In reality once you start your application using pm2, then anytime you login to the production machine where application is deployed and execute 'pm2 env 1' command it shows all the environment variables even if it's a new login session. This is what I want to avoid. I'm think of updating pm2 code to achieve just that unless there is already a way.
– Atarang
Nov 16 '18 at 4:24
add a comment |
I've a node.js application running with some environment variables such as secret_keys, database name etc. All variables are set using export command before starting the server.
I'm using 'pm2' tool to start the server. When I use command 'pm2 env ', it displays all the environment correctly but my question is how to prevent display/showing of few variables such as secret keys, etc.
node.js pm2
asked Nov 15 '18 at 5:10
AtarangAtarang
227416
I've a node.js application running with some environment variables such as secret_keys, database name etc. All variables are set using export command before starting the server.
I'm using 'pm2' tool to start the server. When I use command 'pm2 env ', it displays all the environment correctly but my question is how to prevent display/showing of few variables such as secret keys, etc.
node.js pm2
node.js pm2
asked Nov 15 '18 at 5:10
AtarangAtarang
227416
asked Nov 15 '18 at 5:10
AtarangAtarang
227416
asked Nov 15 '18 at 5:10
AtarangAtarang
227416
asked Nov 15 '18 at 5:10
AtarangAtarang
227416
asked Nov 15 '18 at 5:10
AtarangAtarang
227416
227416
did you have any configuration for pm2 or pass environment as command line
– front_end_dev
Nov 15 '18 at 6:50
No configuration but just following few variables, export USER_PASSWORD="xxxxxxxx"; pm2 start server.js
– Atarang
Nov 15 '18 at 9:15
You can manage this using custom configuration of pm2. Read more about from pm2.io/doc/en/runtime/guide/ecosystem-file/…
– front_end_dev
Nov 15 '18 at 11:48
Setting environment is okay. In reality once you start your application using pm2, then anytime you login to the production machine where application is deployed and execute 'pm2 env 1' command it shows all the environment variables even if it's a new login session. This is what I want to avoid. I'm think of updating pm2 code to achieve just that unless there is already a way.
– Atarang
Nov 16 '18 at 4:24
add a comment |
did you have any configuration for pm2 or pass environment as command line
– front_end_dev
Nov 15 '18 at 6:50
No configuration but just following few variables, export USER_PASSWORD="xxxxxxxx"; pm2 start server.js
– Atarang
Nov 15 '18 at 9:15
You can manage this using custom configuration of pm2. Read more about from pm2.io/doc/en/runtime/guide/ecosystem-file/…
– front_end_dev
Nov 15 '18 at 11:48
Setting environment is okay. In reality once you start your application using pm2, then anytime you login to the production machine where application is deployed and execute 'pm2 env 1' command it shows all the environment variables even if it's a new login session. This is what I want to avoid. I'm think of updating pm2 code to achieve just that unless there is already a way.
– Atarang
Nov 16 '18 at 4:24
did you have any configuration for pm2 or pass environment as command line
– front_end_dev
Nov 15 '18 at 6:50
did you have any configuration for pm2 or pass environment as command line
– front_end_dev
Nov 15 '18 at 6:50
No configuration but just following few variables, export USER_PASSWORD="xxxxxxxx"; pm2 start server.js
– Atarang
Nov 15 '18 at 9:15
No configuration but just following few variables, export USER_PASSWORD="xxxxxxxx"; pm2 start server.js
– Atarang
Nov 15 '18 at 9:15
You can manage this using custom configuration of pm2. Read more about from pm2.io/doc/en/runtime/guide/ecosystem-file/…
– front_end_dev
Nov 15 '18 at 11:48
You can manage this using custom configuration of pm2. Read more about from pm2.io/doc/en/runtime/guide/ecosystem-file/…
– front_end_dev
Nov 15 '18 at 11:48
Setting environment is okay. In reality once you start your application using pm2, then anytime you login to the production machine where application is deployed and execute 'pm2 env 1' command it shows all the environment variables even if it's a new login session. This is what I want to avoid. I'm think of updating pm2 code to achieve just that unless there is already a way.
– Atarang
Nov 16 '18 at 4:24
Setting environment is okay. In reality once you start your application using pm2, then anytime you login to the production machine where application is deployed and execute 'pm2 env 1' command it shows all the environment variables even if it's a new login session. This is what I want to avoid. I'm think of updating pm2 code to achieve just that unless there is already a way.
– Atarang
Nov 16 '18 at 4:24
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53312801%2flimiting-pm2-env-to-display-environment%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53312801%2flimiting-pm2-env-to-display-environment%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
did you have any configuration for pm2 or pass environment as command line
– front_end_dev
Nov 15 '18 at 6:50
No configuration but just following few variables, export USER_PASSWORD="xxxxxxxx"; pm2 start server.js
– Atarang
Nov 15 '18 at 9:15
You can manage this using custom configuration of pm2. Read more about from pm2.io/doc/en/runtime/guide/ecosystem-file/…
– front_end_dev
Nov 15 '18 at 11:48
Setting environment is okay. In reality once you start your application using pm2, then anytime you login to the production machine where application is deployed and execute 'pm2 env 1' command it shows all the environment variables even if it's a new login session. This is what I want to avoid. I'm think of updating pm2 code to achieve just that unless there is already a way.
– Atarang
Nov 16 '18 at 4:24