||7 months ago|
|.github/workflows||7 months ago|
|src||7 months ago|
|.gitignore||7 months ago|
|Cargo.lock||7 months ago|
|Cargo.toml||7 months ago|
|LICENSE||7 months ago|
|README.md||7 months ago|
Simple command to enable updating docker-compose based applications.
If newer containers are available than those running, pull the new containers, and cycle the containers. Supports specifying multiple containers using globs, and multiple globs if necessary.
- Only cycle application if containers were updated (unless
- Don't try and update stopped containers (unless
"How does it work?"
- List images
- If there are images, pull (
- List images again
- If images list is different, cycle container (
docker-compose down && docker-compose up -d)
"How's this different from
After writing this, turns out that
docker-compose support doing most of this for you.
If there are existing containers for a service, and the service’s configuration or image was changed after the container’s creation,
docker-compose uppicks up the changes by stopping and recreating the containers (preserving mounted volumes).
Therefore, you can easily achieve this by simply pulling each compose file, and running
up -d. Which changes all this Rust into a handful of lines of Bash.