Go to file

Claude 8024015b9e tower 0.61.21 — migrate + template-deploy use tenant CF resolver

Phase C made instance-create tenant-aware for Cloudflare DNS, but
migrate.go and templates_deploy.go kept using the legacy global
*cloudflareClient (zone=odoosky.org). Result: a tenant migrate to
4th.online silently created the A record under odoosky.org as a
literal subdomain ('odoo16v2.tenants.4th.online.odoosky.org' →
right IP) — Tower logged 'DNS A record set' successfully because
the API accepted the call, but the actual hostname the user
browses to was never published to the right zone.

Both flows now use cfResolver.clientFor(tenantID, fqdn) to find
the tenant's CF token + correct zone. If no token covers the
domain, the op fails with a clear 'configure tenant CF token'
message instead of silently writing to the wrong zone.

2026-04-30 17:31:44 +03:00

templates

tower 0.61.8 — Phase H substrate completeness

2026-04-30 12:50:25 +03:00

backend-deployment.yaml

tower 0.9.0 + tower-ui 0.8.0 — capacity bars on Server Detail

2026-04-26 20:47:11 +03:00

Chart.yaml

Initial Tower chart

2026-04-26 18:01:44 +03:00

ingressroute.yaml

tower 0.9.0 + tower-ui 0.8.0 — capacity bars on Server Detail