4 ms·
Exactly, for over 4 years I've been using my trusty 10 lines of bash (most of them is confirmation) to deploy in seconds and with 0 downtime. I should probably
by xandrius 2y ago
Exactly, for over 4 years I've been using my trusty 10 lines of bash (most of them is confirmation) to deploy in seconds and with 0 downtime. I should probably opensource it, lol
- Wilduck 2y agoI know you're joking a little, but I personally would love to see them! I'm very interested in how people manage simple deploys.
- tbocek 2y agoHere is mine, I have a docker compose file locally, and this deploy.sh script deploy to my remote machine. That also means that my remote machine is building the image. And I have not found a good solution for secrets/env files yet: #!/usr/bin/env bash export DOCKER_HOST="ssh://username@host:port" docker compose up -d --build
- xandrius 2y agoFor secrets, just literally have an ssh command which reads the local .env file and uses them to start the server with them as arguments/env vars.
- _-_-__-_-_- 2y agoI want to do something similar, but I have multiple compose files, one per project, I haven’t figured out how to script this yet in subfolders.
- mdaniel 2y agohuh, TIL - I had never seen a non-(unix|https) version of DOCKER_HOST time="2025-03-10T08:39:06-07:00" level=debug msg="commandconn: starting ssh with [-o ConnectTimeout=30 -T -l ec2-user -- ip-10-0-2-3 docker system dial-stdio]" and I guess I could be forgiven since $(docker system dial-studio --help) says nothing
- leosanchez 2y agoDo you use symlinks to achieve 0 downtime ? Assuming it is a systemd service ?. If possible could you share gist of that script ?