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?
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!
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.
Click below to sign up and get $200 of credit to try our products over 60 days!
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:
Docker and GitHub Actions
Video: Deploying to DigitalOcean With GitHub Actions
Hope that this helps. Regards, Bobby