Updates and the update check

Updating should be a command, not a project.

Update #

eddy update

Or name a version: eddy update 1.4. The command:

1. takes a backup
2. pins the new version in .env
3. pulls the new image and restarts
4. waits for the health check

If the new version does not become healthy, it puts the old version back. Migrations do not roll back, so it then asks whether to restore the backup it just took. With --yes it only prints the restore command. See backups.

What changed in each release is in the changelog.

The update check #

Once a day the app fetches https://get.eddyline.app/releases.json and shows staff “Version 1.3 is available” on /admin/settings. The file lists the latest version, its date and a link to the notes, plus every release with its date. The licence banner uses that list to name the last version your updates cover.

The request carries no cookies, no licence and no workspace data. Its user agent is eddy/<version>, and like any request it shows your server’s IP address to the host. It is the only outbound call the app makes by itself.

Turn it off #

Set UPDATE_CHECK=false with eddy config. You will no longer see new versions in the app, and the licence banner will say “an earlier version” instead of naming one. Everything else works the same.

See what leaves the server for every connection Eddyline makes.