mirror of
https://github.com/jhd3197/ServerKit.git
synced 2026-11-03 02:26:43 +09:00
Juan DenisandClaude Fable 5
fb8d6bfbf8
The drawer showed '<name>.<base> — Published automatically once the deploy finishes' whenever a managed base domain existed, but publishing was gated on a per-template auto_domain flag the operator can't see. For most of the catalog the install landed on host:port instead — a link a default firewall doesn't even expose — and the domain had to be redone by hand in the service's Domain settings. The promise on screen is now the contract: when the drawer displays a domain it sends auto_domain: true, which rides the install plan to the finalizer and overrides the template's silence (the forced flag also feeds the SERVICE_FQDN magic context, so tokens and the published host agree). Absent flag = the template YAML still decides, as before. The drawer also stops promising what can't be delivered: the domain field only renders for compose templates targeting the local server — the panel's nginx can't proxy a remote container, and the repo pipeline has no auto-publish step. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>