v0.4.19

New

• Edit a domain like you add one: its name, route or redirect, port, Cloudflare Tunnel or server IP, HTTPS and certificate, and its Cloudflare DNS record and proxy.
• Compose stacks can roll back. Each deployment records its compose file, commit and images, and a rollback runs exactly those. Deployments made before this release cannot roll back.
• Status pages: Serve creates the A record of their domain when a connected Cloudflare account manages it, and removes it with the page. A Create A record button fixes a missing one.
• Preview comments on GitLab, Gitea/Forgejo and Bitbucket, as on GitHub.
• ClickHouse has a Users tab: add logins, change passwords and access, delete them.
• The API covers what the dashboard does: status pages, database pooler and public access, main database, deploy rules and approvals, HTTP options, compose storage, request log settings, preview databases, server variables, OS updates, Cloudflare, Git credentials, repository webhooks and tailnets.
• The CLI gained database replicas, settings, public port and domain, preview and replica variables, tokens create, the request log, compose backups, proxy actions, trusted proxies, status page incidents and branch clean-up SQL.

Fixed

• Promoting a read replica could leave the old database running, so two writable copies. It now stops unless the old one is confirmed gone.
• ClickHouse in compose stacks was never offered for backups. It is now, and every one of its databases is backed up, not only default.
• A renewed certificate that a proxy could not load passed as loaded. It is now shown on the certificate and alerted.
• Removing a domain, service or project hid DNS records, replicas and certificates it could not remove. You now get a warning, and the activity log keeps it.
• Anyone who could comment on a pull request could get Serve to edit their comment instead of its own. Existing GitHub preview comments get one new comment on the next deploy.
• The primary domain could be turned into a redirect.
• Restore errors from ClickHouse and MongoDB showed a useless line instead of the reason.
• API paths were decoded more than once, so a compose backup key with / or % needed odd encoding. Encode once now.

Polished

• Every site serves the best certificate covering its name: its own before a wildcard, then the one valid longest. The status page picker says which one Automatic uses.
• A failed preview DNS record is reported instead of a link that does not work.
• Over 80 new tests for the job queue, backups, certificates, nginx sites, variables and shell quoting.

Commits

• 8ef9a890 Edit domain: the port sits beside the name
• 235a87fa Domains: the primary one cannot become a redirect; status page DNS records are changed by admins only, as for app domains
• 2f191759 Domains: edit everything as when adding: name, route or redirect, port, tunnel or IP, HTTPS and certificate, and the Cloudflare record and its proxy
• c19b84e7 Preview comments are found by a marker only this instance can make, so a copied marker never gets someone else's comment edited
• 36ec0086 Certificates: every site serves the best one covering its name (its own before a wildcard, then the longest valid); Automatic says which
• 377d4807 Status pages: Serve makes the A record of their domain when a connected Cloudflare account manages it, and removes it with them
• 2d91daec Test: the truncated-backup check gets time for its four slow key derivations
• 606f3cbb API: paths are decoded once, so a compose backup key with / or % is one segment encoded once
• 987bf31b Restore errors name ClickHouse's and mongorestore's own reason, not the line after it
• 78018e11 CLI: database replicas, settings, public port and domain; preview and replica variables; tokens create; request log; compose backups; proxy actions and trusted proxies; status page incidents; branch clean-up SQL
• 68f10e9e API: connect and disconnect Cloudflare and change zone settings, add and remove Git tokens and deploy keys, repository webhooks, and tailnets
• d9d5794c Compose stacks can roll back: each deployment records its compose file, commit and images, and a rollback runs exactly those
• 8106bdf4 API: server variables, redeploying what uses shared variables, OS updates, default server, an app's main server, and the instance's proxy configuration
• 348692ab Removals say what they could not take with them: DNS records, replicas, certificates, tunnel routes; the activity log keeps it
• 70bf1c23 API: HTTP options and custom proxy site, compose storage, request log settings, preview databases and pointing a domain at the main server
• 620a8fe4 Test custom certificates, nginx site rendering, variable resolution and shell quoting
• 819d413b Test backup encryption, import helpers, checksums and restore targets
• 2334ffe1 Test job queue claim, finish, fail and recovery statements
• d45ac9cd Preview comments on GitLab, Gitea/Forgejo and Bitbucket, edited on removal; a preview DNS record that fails is said, not linked
• 2824c389 Certificates: what could not load one is counted for everyone and named only in its log
• 9b7ab031 API: database pooler and public access, main database, certificate retry, redeploying services, deleting volumes, and deploy rules
• d1ae7d21 Certificates: a proxy or database that could not load a new or renewed one is shown on it and alerted
• a8ce77f8 Users tab for ClickHouse: list, add, change password, access and delete logins
• 854ecf27 API: create, change and delete status pages, their domain, visibility, subscriptions, components and subscribers
• 08d23b2b Promoting a replica stops unless the old database is confirmed gone; its public domains go only once promoted
• 80048b10 Compose stacks: ClickHouse is found for backups, and every one of its databases is backed up