Skip to content

compose: keep traefik's file provider through a deploy - #105

Merged
max-tet merged 1 commit into
mainfrom
fix/compose-traefik-file-provider
Sep 21, 2026
Merged

max-tet merged 1 commit into
mainfrom
fix/compose-traefik-file-provider

Conversation

@ClaydeCode

Copy link
Copy Markdown
Owner

The bug

The deploy job scp's this repo's docker-compose.yml over /home/ubuntu/clayde/docker-compose.yml and then runs docker compose up -d. Anything the VM copy carries and this one does not is therefore dropped on every merge to main.

Two traefik settings were in that category:

  • --providers.file.directory=/dynamic and --providers.file.watch=true
  • the ./traefik-dynamic:/dynamic:ro mount

They serve ~/clayde/traefik-dynamic/board.yml and walk.yml, the hand-written routes for the /board and /walk backends that run on the host rather than as containers here.

Evidence

After today's deploy of #104, https://clayde.net/board and https://clayde.net/walk both returned 404 — traefik's answer when no router matches, as opposed to the 502 a dead backend would give. The VM copy had to be patched back by hand. This was the second occurrence today: the 11:25 UTC deploy did the same thing, which is what docker-compose.yml.bak-2026-09-21-1138 on the VM records.

The fix

Put both settings in the deployed file, so the scp carries them instead of removing them.

The deploy job scp's this file over /home/ubuntu/clayde/docker-compose.yml
before running `docker compose up -d`, so anything the VM copy has and
this one lacks is silently dropped on every merge to main. The file
provider and its /dynamic mount were in that category: they serve the
hand-written routes for the /board and /walk backends running on the
host, which returned 404 after today's deploy until the VM copy was
patched back by hand. Second occurrence today.
@max-tet
max-tet merged commit aee3fd0 into main Sep 21, 2026
3 checks passed
@max-tet
max-tet deleted the fix/compose-traefik-file-provider branch September 21, 2026 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants