Upgrading

Upgrade Scryer during a quiet window, when no one is actively resolving imports or editing settings.

The safest upgrade rhythm is simple: preserve the data directory, move the binary or image forward, then verify a few core screens before treating the instance as normal again.

Docker Compose

docker compose pull
docker compose up -d

Keep /config and media roots mounted outside the container image.

Homebrew

brew update
brew upgrade scryer
brew services restart scryer

If you need a same-version Homebrew packaging fix immediately, run:

brew update --force
brew reinstall scryer

Manual Binaries

Stop Scryer, replace the binary from the latest release, and start Scryer again with the same data directory. Reusing the same data directory preserves users, settings, libraries, and operational history.

Upgrade Checklist

• Keep database and config storage persistent.
• Verify the System page after startup.
• Open one facet overview and one Settings page to confirm the UI is healthy end to end.
• If you run companion services, upgrade them independently according to their own release guidance.

Related Concepts

• Installation — install reference for Docker, Homebrew, and manual binaries
• System Overview — confirm the instance is healthy after an upgrade
• System Jobs — verify background jobs resume normally post-upgrade