[Wilduck]

I 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]

Here 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]

For 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.

[_-_-__-_-_-]

I 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]

huh, 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