What problem will this feature address?
Currently the only way to remove a domain from a service is to delete it. That's inconvenient when a domain is only needed occasionally — for example, enabling it temporarily to check external access to a service — because re-adding it means re-entering the host, port, certificate and path every time.
Describe the solution you'd like
Add an enabled flag to domains and a switch in the Domains tab to turn a domain on/off without deleting it, keeping its configuration intact.
- Applications: routing is file-provider based, so disabling removes the traefik router immediately and enabling recreates it.
- Compose: domains are rendered as docker labels, so the change applies on the next deployment (a "redeploy required" hint is shown).
Defaults to enabled = true, so existing domains are unaffected.
Describe alternatives you've considered
Deleting and re-creating the domain each time (the current behavior) — this loses the configuration and is error-prone. There is no UI way to keep a domain configured but inactive.
Additional context
Typical use case: a self-hosted service (e.g. a camera/NVR) whose domain is exposed only occasionally to verify external access — the rest of the time it should stay configured but inactive, without having to delete and recreate it.
Will you send a PR to implement it?
Yes
What problem will this feature address?
Currently the only way to remove a domain from a service is to delete it. That's inconvenient when a domain is only needed occasionally — for example, enabling it temporarily to check external access to a service — because re-adding it means re-entering the host, port, certificate and path every time.
Describe the solution you'd like
Add an
enabledflag to domains and a switch in the Domains tab to turn a domain on/off without deleting it, keeping its configuration intact.Defaults to
enabled = true, so existing domains are unaffected.Describe alternatives you've considered
Deleting and re-creating the domain each time (the current behavior) — this loses the configuration and is error-prone. There is no UI way to keep a domain configured but inactive.
Additional context
Typical use case: a self-hosted service (e.g. a camera/NVR) whose domain is exposed only occasionally to verify external access — the rest of the time it should stay configured but inactive, without having to delete and recreate it.
Will you send a PR to implement it?
Yes