24 ms·
>I much prefer Render.com and DigitalOcean's setup where you select a repo and then it takes care of the rest with auto update on git push. Doesn't that force
by mtlynch 4y ago
>I much prefer Render.com and DigitalOcean's setup where you select a repo and then it takes care of the rest with auto update on git push.
Doesn't that force you to use your hosting provider as your CI provider?
I've always avoided the automatic "deploy on git push" solutions because I want to keep my CI provider uncoupled from my hosting provider. That way, I can switch hosts without having to rewrite all my CI code.
- tuukkah 4y agoTo keep CI and hosting decoupled, your CI can push fresh images to a docker registry, and your deployment can poll for updated images. An easy way to achieve this is to add the Watchtower container to your compose files: https://containrrr.dev/watchtower/running-multiple-instances/ https://containrrr.dev/watchtower/running-multiple-instances...
- mtlynch 4y agoI don't think that's a good solution in general unless you're confident that all of your deployments will use Docker Compose. About 1/3 of my deployments are just static sites, and the rest all fit into a single Docker container, so integrating Compose would be a big increase in complexity.
- tuukkah 4y agoI'd say Compose simplifies even your single-container deployments, as the compose file is the single place to set your env variables, port forwards etc. That being said, you can use Watchtower without Compose. It's enough to run docker run -d -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower