Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Hi,
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?
Laveenk16
SonuKrJe
016512ea60864da0867e5280f293de
f9ccf41c1c3743eb9a1071f9dae7a7
KFSys
9e88c3e13bc3486b8d5b03587df754
Shaun
grime3ja
JSA+Partners Admin
Mark Reeves
Whathetech
1cc989f14bd449869796256cff236f