For example, heroku has a option in app settings to enter environment variable.
yes, in heroku there is an option to store that. but how if we use own server?
Like this
// keys.js ====== module.exports = { PORT: process.env.PORT, WHO_AM_I: process.env.WHO_AM_I, };
ok, thank you.
But, still we're using 'process.env', which uses to 'dotenv' package in production?
In production I didn't use .env, I store all credentials on host environment or if I use docker, I store it in docker secrets.
Cool, thanks!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For example, heroku has a option in app settings to enter environment variable.
yes, in heroku there is an option to store that. but how if we use own server?
Like this
ok, thank you.
But, still we're using 'process.env', which uses to 'dotenv' package in production?
In production I didn't use .env, I store all credentials on host environment or if I use docker, I store it in docker secrets.
Cool, thanks!