A space to discuss and keep up software development and manage your software career
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
An inclusive community for gaming enthusiasts
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
A community of golfers and golfing enthusiasts
A collaborative community for all things Cryptoβfrom Bitcoin to protocol development and DeFi to NFTs and market analysis.
Discussing the core forem open source software project β features, bugs, performance, self-hosting.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating
dotenv is a dev dependency. In production, keys are stored on the server which can be accessed by node without using dotenv
dotenv
Yes thats right that we store keys on server. But what about the dotenv package we imported into file and written as process.end.VAR_NAME ? Wont it require to use dotenv package?
keys
process.end.VAR_NAME
can you give me little example how storing keys on production? thank you
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.
dotenvis a dev dependency. In production, keys are stored on the server which can be accessed by node without usingdotenvYes thats right that we store
keyson server.But what about the dotenv package we imported into file and written as
process.end.VAR_NAME? Wont it require to usedotenvpackage?can you give me little example how storing keys on production? thank you
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!