Updating GRIDer
New releases ship as new Docker images. Updating is always a deliberate step you trigger yourself — nothing updates itself behind your back, and your data and settings are preserved across an update. Your grids pause for the restart and resume automatically.
There are two ways to update, depending on how you installed:
- From the app (one click) — for instances set up with the one-click installer. Recommended.
- From the server (manual) — for instances you installed by hand, on localhost, or with a custom setup.
Update from the app (recommended)
If your instance was provisioned by the installer, it can update itself with a button — no SSH, no terminal.
- When a new version is available, a small version badge in the top menu (for example
v1.0.3) shows a green dot. Only the owner wallet sees it. - Click the badge. A window shows your current version → the new version and a reminder that the app restarts.
- Click Update now.
The instance then downloads the new image and restarts. This takes 1–2 minutes, during which the app is briefly unavailable. Keep the window open — it tells you when the update has finished. When it's done, reload the page to load the new interface, and check that your grids resumed.
Safety net: if the new version fails to start, the instance automatically rolls back to the previous one and your grids keep running. Your .env, database and secrets volume are never touched.
Why a button and not automatic updates? GRIDer never updates itself silently: you decide when to move, and the update runs entirely on your server. The button just saves you a trip to the command line.
Update from the server (manual)
For a manual, localhost or custom install (no one-click updater), update from the shell. On your server, in the install directory (default /opt/grider):
- Edit
.envand change the version tag to the new one, e.g.:1.0.3→:1.0.4:GRIDER_IMAGE=registry.grider.xyz/grider-selfhost:1.0.4 - Pull and restart:
docker compose pull docker compose up -d
On start-up the new version applies any database changes automatically (they're additive and safe to re-run), your grids resume, and your instance secrets and history stay in their Docker volumes.
- The registry login from your original install is remembered, so the pull just works. If it ever asks for credentials, they were the ones provided with your licence.
- Your
.env, your database and your secrets volume are not touched by an update.
How versions are pinned
Your install pins an exact image version in its environment file (/opt/grider/.env):
GRIDER_IMAGE=registry.grider.xyz/grider-selfhost:1.0.3
Because the version is pinned, docker compose pull on its own re-fetches the same version — it doesn't jump to a newer one. That's intentional: upgrades happen when you decide. The in-app button changes this tag for you (to the exact published version) and restarts; the manual method is you doing the same by hand.
Finding the current version
The badge in the app tells you both your current version and whether a newer one is available. The newest published version also appears on the install page and is announced in the community channels. If you're unsure whether an update is worth taking, ask in Discord.
If an update misbehaves
The in-app update already rolls back automatically if the new version doesn't start. To move back manually — versions are just image tags — set the older tag in .env and run docker compose pull && docker compose up -d. For anything involving your data, ask in Discord first — and grab your logs so we can help quickly.