v1.0.0-beta.4

In short: ops watches your sites every minute and mails you when one goes down, puts apps and servers in your order, and updates itself and your servers.

New

• Uptime checks, built in: ops checks every domain of every app from outside once a minute, from the first deploy on, with nothing to set up. The app's Uptime tab shows 24 hours, 7 and 30 days, the certificate and the last outages. Also ops uptime, the TUI (u on an app), API and MCP. (#18)
• Your own order: Drag apps and servers where you want them, or use ops apps move blog top, or K / J in the TUI. Everyone in the workspace sees the same order everywhere. (#14)
• List or grid: Switch how the Apps and Servers pages look. ops remembers it for you. (#14)
• Update now: A self-hosted ops shows when a release is out, with its notes. It updates in one click. If the new version does not start, the old one comes back. Also ops update. (#8)
• Servers update themselves: Each one moves to the hub's version, one server at a time and never during a deploy. Turn it off with ops servers auto-update off. (#8)
• Email alerts: Owners and admins get a mail when a site goes down or comes back, a server goes offline or a deploy fails. Turn it off for you with ops alerts off.

Changed

• Activity: A server going offline and coming back now shows there. So does every site that goes down and comes back. (#18)
• Self-hosted gets releases only: update.sh takes the newest release, not every build in between.
• A copy of the database before every upgrade: ops writes backup-before-<version>.db next to it before it changes the schema. (#8)

Fixed

• Signing in with GitHub finds your account: It uses any verified email on your GitHub account, not only the primary one. It no longer makes a new empty account. (#24)

Upgrade

Self-hosted: run git pull in the repo, then sh update.sh once. It also starts the updater. From then on, use Update now.