Update

One update, one click. From Settings -> Deplo -> Updates, Deplo updates the panel, restarts it, and then brings every connected server to the same version on its own, one server at a time.

• The control plane (this panel) goes first.
• The server agents - one per host - follow once the panel is back.
• Database migrations run automatically at startup.

Agent updates only ever move forward. There is no downgrade path.

Release historyCopy Anchor Link

Settings -> Deplo -> Updates shows the installed version, available releases, release notes, and agent versions across the fleet.

• Check now refreshes the release list.
• The installed release is marked Installed.
• The page shows which agents are behind.

Update the control planeCopy Anchor Link

Three things happen around it that are worth knowing:

• A pg_dump of the panel's database lands in /opt/deplo/backups first, and the newest three are kept.
• Secrets are never rotated, and no setting is reset.
• If the new version does not come up, the previous one is put back automatically. The panel says so instead of leaving you on a spinner.

If the panel cannot update itselfCopy Anchor Link

Run the installer on the control-plane host instead:

curl -fsSL https://deplo.build/install.sh | bash

The existing /opt/deplo/.env switches the installer to update mode.

To pin a version rather than take the newest:

curl -fsSL https://deplo.build/install.sh | \
  DEPLO_VERSION=0.1.0 bash

The agents follow on their ownCopy Anchor Link

Once the panel is back, Deplo walks the fleet by itself: remote servers first, the machine Deplo runs on last, one at a time. The Server agents card on the Updates tab counts them down, and every agent it updates is recorded in Activity under your name.

A server is skipped when Deplo cannot touch it safely, and it is named on that card with a link to it:

• A deploy is running on it. An update restarts the agent, which would drop the build.
• It is unreachable right now.
• Its agent is too old to update itself. Re-run the install command from the server's Advanced tab.

Deplo retries a skipped server every 15 minutes until it is up to date, so a busy host catches up on its own.

Update one server by handCopy Anchor Link

You never have to, but you can - open Settings -> Servers, open the server, and click the Update to button on its Overview tab. It only appears when that host is behind.

Before you update againCopy Anchor Link

• Agents cannot be downgraded. Test on a canary.
• Some features need a newer agent. When one is missing, Deplo says so rather than silently doing something else.
• Re-running the installer is safe. It is what the button does, so running it by hand is never a workaround.
• Read the release notes for a minor bump. During 0.x, minor means something you notice: a feature, changed behavior, a database migration, or a newer agent required.
• Back up before a big jump. Migrations apply at boot and are not reversed by rolling the image back.

TroubleshootingCopy Anchor Link

Panel that won't come back after an update, an image that won't pull, or an agent update that fails: see Servers and agents troubleshooting.

Next stepsCopy Anchor Link