CI/CD: Avoid restarting unaffected services on every push to main #1

New Issue

Kappeh · 2026-01-30T23:42:04Z

Kappeh commented

2026-01-30 23:42:04 +00:00

At present, pushes to the main branch trigger a deployment that restarts the entire Docker Compose stack, even when changes only affect a subset of services or non-runtime files (e.g. documentation).

This is functional but sub-optimal for availability, especially given that most services are independent and configuration changes are often scoped to a single container.

This issue tracks an enhancement to make deployments service-aware, so that only services whose configuration or dependencies have changed are restarted.

At present, pushes to the `main` branch trigger a deployment that restarts the entire Docker Compose stack, even when changes only affect a subset of services or non-runtime files (e.g. documentation). This is functional but sub-optimal for availability, especially given that most services are independent and configuration changes are often scoped to a single container. This issue tracks an enhancement to make deployments service-aware, so that only services whose configuration or dependencies have changed are restarted.

Kappeh added the Kind/Enhancement

Priority

Low

4

labels 2026-01-30 23:42:04 +00:00

Kappeh self-assigned this 2026-01-30 23:42:04 +00:00

Kappeh added reference main

2026-02-01 19:36:07 +00:00

Kappeh added this to the Issue Board project 2026-02-01 19:37:30 +00:00

Kappeh moved this to To Do in Issue Board on 2026-02-01 19:52:17 +00:00

Kappeh moved this to Backlog in Issue Board on 2026-02-01 19:52:19 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Homelab/minecraft_server#1

CI/CD: Avoid restarting unaffected services on every push to main #1

CI/CD: Avoid restarting unaffected services on every push to `main` #1