What is the best approach to storing and deploying environment variable files to Node.js if they are excluded from version control?

Asked May 01 '19 at 13:12

Active May 01 '19 at 13:12

Viewed 346 times

Firstly a tiny bit of background: I have a MEAN stack application running on Bitnami Ubuntu, on AWS. I have a .env file with API keys etc in it, that is excluded from my repo using .gitignore.

I understand the main approaches to initialising the application to pick up the .env file, but none of the articles which describe these comment on (1) what options are there to deploy your .env to your server if it's not in your git repo, and (2) if it's not stored in version control, where might it be best to keep that .env file so that it's secure?

Others experiences of this would be very valuable. I couldn't find anything similar on Google, SO or SF.

Thanks.

asked May 01 '19 at 13:12

Mandrake... Mandrake.

The idea is that you use versioning for maintaining your code base and *”configuration management”* to govern which release should be deployed where and with what settings. – HBruijn May 01 '19 at 14:26
This depends on how you're deploying your app. But there is always somewhere to put the environment variables. – Michael Hampton May 01 '19 at 16:17
I've got more of a handle on what to search for now. Thank you both very much. – Mandrake... Mandrake. May 02 '19 at 08:56

What is the best approach to storing and deploying environment variable files to Node.js if they are excluded from version control?

0 Answers0