.env file, ENV vars, or something else?


Does Digital Ocean have something similar to Credstash or AWS Secrets Manager (both AWS services)?

Trying to decide on the most secure way to store environmental variables with sensitive information (like database access codes, for example).

Locally, I have .env file that is named in my .gitignore to prevent them being version controlled.

What is the best (i.e. most secure) way to store sensitive .env information?

If just in a .env file or environment variables, what’s the best way to keep that secure when the droplet contains a publicly facing GUI?

Much appreciated :)


Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Has anybody answered this?

how do we store env vars on DO? does it simply read the .env as with local? is this a secruty issue? or is there a way similar to AWS where we crea key-val pairs in our DO account?