3 ms·
I tend to have a compose file that is designed to be used with `envsubst` for deployment via the CI, so a CI specific template. This way the CI can create the f
by layoric 4y ago
I tend to have a compose file that is designed to be used with `envsubst` for deployment via the CI, so a CI specific template. This way the CI can create the final file and `scp` it over to the host before calling `docker compose up`. The file always ends up with the same name and same location on the host so `docker compose` can detect any changes. So far haven't had any issues, but definitely not as clear as having `compose.dev.yml`/`compose.prod.yml` in source control, though very flexible.
Made a video of using this pattern with Blazor WASM, SQLite and Litestream here [1].
[1] https://youtu.be/fY50dWszpw4 https://youtu.be/fY50dWszpw4