Skip to content

Fix(hello-world-dotnet): fix caddy for new service#27

Merged
krellekrelle merged 3 commits into
mainfrom
fix/dotnet-hello-world
May 27, 2026
Merged

Fix(hello-world-dotnet): fix caddy for new service#27
krellekrelle merged 3 commits into
mainfrom
fix/dotnet-hello-world

Conversation

@krellekrelle

Copy link
Copy Markdown
Owner

No description provided.

- Replace custom frontend with @platform/ui-library components (NavBar,
  Card, Button) — identical pattern to hello-world-app
- Fix Dockerfile to use monorepo root as build context so ui-library
  source is accessible during the React build stage
- Fix docker-compose build context to match (context: ., dockerfile: ...)
- Fix hardcoded JWT_SECRET in docker-compose → use ${JWT_SECRET} env var
- Add hello-world-dotnet-app to CI matrix with root build context
- Add ui-library/** to dotnet path filter so UI changes trigger a rebuild
Caddy was serving stale routing config (no /hello-dotnet/*) because it
runs for weeks without restarting and docker compose up -d does not
signal it to reload when only the Caddyfile volume content changes.

Add a 'caddy reload' step after 'docker compose up -d' so any Caddyfile
changes take effect immediately on every deploy.
Docker file bind mounts pin the inode at container start time. When git
pull replaces the Caddyfile (new inode), the running Caddy container
still sees the old inode via the bind mount, so caddy reload reads stale
config.

Fix: pipe the Caddyfile content from the host into a temp file inside
the container, then reload from that — bypasses the stale bind mount.
@krellekrelle
krellekrelle merged commit 45c9549 into main May 27, 2026
1 check passed
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.

1 participant