What problem will this feature address?
Preview Deployments always route through Traefik's default web/websecure entrypoints, with no way to override them.
Regular application domains already expose a Custom Entrypoint control (the useCustomEntrypoint toggle → domains.customEntrypoint), so if your Traefik static config defines additional or custom entrypoints (e.g. a dedicated listener/port), regular services can use them. Preview deployments have no equivalent, so their auto-generated domains are stuck on web/websecure.
Describe the solution you'd like
Add a Custom Entrypoint setting to an application's Preview Deployment configuration, applied automatically to every auto-generated preview domain — mirroring how previewPath, previewPort, previewCertificateType, and previewCustomCertResolver already work as parent-level defaults.
- New
previewCustomEntrypoint value on the application's preview settings.
createPreviewDeployment passes it into createDomain, and the existing manageDomain call writes it into the Traefik dynamic config (no manual step).- Preview Settings gets a
Custom Entrypoint toggle + Entrypoint Name input matching the regular domain form. Empty/off reverts to the default web/websecure.
Describe alternatives you've considered
- Per-preview override in the preview domain dialog — rejected, because preview domains are ephemeral and auto-created per PR, so a parent-level default is the practical fit (editing each PR's domain by hand doesn't scale).
- Manually editing the generated Traefik dynamic config — not persistent; it's overwritten on the next deploy
Additional context
The backend already supports customEntrypoint on any domain; this only needs a parent-level default wired through the preview creation path.
Will you send a PR to implement it?
Yes
What problem will this feature address?
Preview Deployments always route through Traefik's default
web/websecureentrypoints, with no way to override them.Regular application domains already expose a Custom Entrypoint control (the
useCustomEntrypointtoggle →domains.customEntrypoint), so if your Traefik static config defines additional or custom entrypoints (e.g. a dedicated listener/port), regular services can use them. Preview deployments have no equivalent, so their auto-generated domains are stuck onweb/websecure.Describe the solution you'd like
Add a Custom Entrypoint setting to an application's Preview Deployment configuration, applied automatically to every auto-generated preview domain — mirroring how
previewPath,previewPort,previewCertificateType, andpreviewCustomCertResolveralready work as parent-level defaults.previewCustomEntrypointvalue on the application's preview settings.createPreviewDeploymentpasses it intocreateDomain, and the existingmanageDomaincall writes it into the Traefik dynamic config (no manual step).Custom Entrypointtoggle +Entrypoint Nameinput matching the regular domain form. Empty/off reverts to the defaultweb/websecure.Describe alternatives you've considered
Additional context
The backend already supports
customEntrypointon any domain; this only needs a parent-level default wired through the preview creation path.Will you send a PR to implement it?
Yes