Automatic Deployment on Git: where to put .env


I’m just getting my feet wet with Docker, and automatic deployment to Digital Ocean from git. What are best practices to deal with the .env file? In particular, my repo is public but I’d like to keep the .env file away from prying eyes. It sounds like I would nee to commit it to my deploy branch, but course, I wouldn’t want it in my commits. How can I keep it private while making use of the automatic deployment?

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.

Bobby Iliev
Site Moderator
Site Moderator badge
March 14, 2021
Accepted Answer

Hi there,

Indeed your secrets should not be checked into Git. What you could do instead is add your passwords as secrets in GitHub. That way they will be stored securely and no one will have access to them.

Here are 2 good resources on how to do that:

Hope that this helps. Regards, Bobby

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel