Skip to content

Align template docs with split-horizon DNS #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
iPior merged 1 commit into from
Aug 13, 2026
Merged

Align template docs with split-horizon DNS #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,10 +56,12 @@ Vite proxies `/api/*` to the local API during development.

Production routing belongs to the platform Caddy instance managed by `platform-deploy`.

Each application uses one canonical `<app>.szarans.ca` hostname. The same hostname is used from the trusted LAN and through Tailscale; split-horizon DNS returns the appropriate private address for the client's network context.

The expected pattern is:

```text
<app>.szarans.ca / <app>.ts.szarans.ca
<app>.szarans.ca
|
v
platform Caddy
Expand All @@ -71,6 +73,8 @@ platform Caddy
SPA files only
```

Separate `.ts.szarans.ca` application hostnames are no longer used.

The Caddy process inside the web container is deliberately not a reverse proxy. It only serves the compiled Vite application and falls back to `index.html` for client-side routes. API routing, domains, TLS, and ingress remain platform responsibilities.

## Database
Expand Down
Loading