perf: configure service update configuration#253
Merged
dargmuesli merged 1 commit intofeat/dargstack/v4from Apr 4, 2026
Merged
perf: configure service update configuration#253dargmuesli merged 1 commit intofeat/dargstack/v4from
dargmuesli merged 1 commit intofeat/dargstack/v4from
Conversation
dargmuesli
force-pushed
the
perf/deployment/update-start-first
branch
2 times, most recently
from
32efaff to
beac2a7
Compare
There was a problem hiding this comment.
Pull request overview
This PR updates multiple production service overrides to standardize Docker Swarm rolling-update behavior by setting deploy.update_config.order to start-first, aiming to reduce downtime during service updates.
Changes:
- Added
deploy.update_config.order: start-firstto many existing production service overrides. - Introduced new production override files for several services to apply the same update order.
- Adjusted some existing production overrides (e.g.,
reccoom) to accommodate the newdeploy.update_configstructure.
Reviewed changes
Copilot reviewed 22 out of 22 changed files in this pull request and generated 15 comments.
Show a summary per file
| File | Description |
|---|---|
| src/production/zammad/compose.yaml | Adds start-first update order to multiple Zammad components. |
| src/production/vibetype/compose.yaml | Adds start-first update order to the vibetype service. |
| src/production/tusd/compose.yaml | Adds start-first update order to the tusd service. |
| src/production/traefik/compose.yaml | Adds start-first update order to Traefik and traefik-certs-dumper. |
| src/production/sqitch/compose.yaml | Adds start-first update order to sqitch. |
| src/production/redpanda/compose.yaml | Adds start-first update order to Redpanda services. |
| src/production/redis/compose.yaml | New override applying start-first to redis. |
| src/production/reccoom/compose.yaml | Restructures deploy override and adds start-first. |
| src/production/reccoom_postgres/compose.yaml | New override applying start-first to reccoom_postgres. |
| src/production/prometheus/compose.yaml | Adds start-first update order to Prometheus. |
| src/production/postgres/compose.yaml | Adds start-first update order to postgres-backup and postgres. |
| src/production/postgraphile/compose.yaml | Adds start-first update order to PostGraphile. |
| src/production/portainer/compose.yaml | Adds start-first update order to Portainer. |
| src/production/portainer-agent/compose.yaml | New override applying start-first to portainer-agent. |
| src/production/memcached/compose.yaml | New override applying start-first to memcached. |
| src/production/jobber/compose.yaml | Adds start-first update order to jobber. |
| src/production/grafana/compose.yaml | Adds start-first update order to Grafana. |
| src/production/geoip/compose.yaml | New override applying start-first to geoip. |
| src/production/elasticsearch/compose.yaml | New override applying start-first to Elasticsearch. |
| src/production/debezium/compose.yaml | New override applying start-first to Debezium services. |
| src/production/cloudflared/compose.yaml | Adds start-first update order to Cloudflared. |
| src/production/adminer/compose.yaml | Adds start-first update order to Adminer. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
dargmuesli
force-pushed
the
perf/deployment/update-start-first
branch
from
beac2a7 to
9b1a111
Compare
dargmuesli
changed the title
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 22 out of 22 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
dargmuesli
force-pushed
the
perf/deployment/update-start-first
branch
from
9b1a111 to
8f19907
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request standardizes the deployment update strategy across multiple production Docker Compose services by setting the
update_config.ordertostart-first. This change ensures that, during rolling updates, a new container is started before the old one is stopped, minimizing downtime for critical services.