feat(server): support `Host` header routing #70

New issue

Closed

opened 2025-11-02 18:52:40 +00:00 by treadful · 2 comments

treadful commented

2025-11-02 18:52:40 +00:00

Owner

Add support for Host header routing. Where users could CNAME the server domain with their own and the server will serve the configured key for that host(s).

This would allow each key to have a custom domain.

Difficult considerations are TLS termination and if it's worth setting up something like an ingress and cert manager to handle it. This might be easier later if moving to a kubernetes cluster to scale.

Add support for `Host` header routing. Where users could CNAME the server domain with their own and the server will serve the configured key for that host(s). This would allow each key to have a custom domain. Difficult considerations are TLS termination and if it's worth setting up something like an ingress and cert manager to handle it. This might be easier later if moving to a kubernetes cluster to scale.

treadful added this to the 1.0 milestone

2026-06-24 04:08:26 +00:00

treadful self-assigned this

2026-06-29 04:53:17 +00:00

treadful referenced this issue from a pull request that will close it,

2026-07-01 01:20:32 +00:00

feat(server): adds support for subdomain aliases and domains #141

treadful commented

2026-07-02 01:15:24 +00:00

Author

Owner

Looking at TLS termination. Here are some non-kubernetes options:

Caddy seems like the play. Will follow this up with that as an ops task.

Looking at TLS termination. Here are some non-kubernetes options: - https://caddyserver.com/f - https://github.com/c2FmZQ/tlsproxy - https://doc.traefik.io/traefik/getting-started/ - custom HAProxy solution? https://dzone.com/articles/zero-trust-build-high-scale-tls-termination-layer Caddy seems like the play. Will follow this up with that as an ops task.

treadful commented

2026-07-02 01:16:37 +00:00

Author

Owner

Ref #145

treadful closed this issue

2026-07-02 01:48:18 +00:00