You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expand managed hostnames from the Cluster Domain row, not the runtime frame #1021
Deploys and the UI take the generated name from the Organization's Cluster Domain row instead of the runtime watch frame. Managed hostnames reach the daemon already expanded as explicit prefix.name hostnames, and generated URLs render with no Server connected.
Acceptance criteria
Deploy compile reads the row and emits ${prefix}.${name} as explicit hostnames; the daemon never receives a bare prefix.
With no row, deploy attempts one inline reserve, then refuses with a named failure pointing to Server Settings.
PLOYZ_PUBLIC_DOMAIN expansion uses the row; servicePublicDomain keeps its signature.
The Service drawer, variables tab and reference targets read the name from an Organization query; "pending" links to Server Settings; the up.ployz.dev placeholder is gone.
Nothing in Cloud reads hosted_dns_hostname from the runtime frame.
Activity