OpsVibes Docs

Updating and uninstalling

Upgrade to a new release, back up the panel and remove OpsVibes from a server.

Updating

Panel data lives in /etc/opsvibes and is kept across updates. Running apps keep running.

When a new release is out, the panel sidebar shows a New badge. Click it (or open Settings → Version and updates) and press Update.

The panel downloads the release, restarts with the same configuration and waits until the new version is healthy. If it does not start, the panel rolls back to the version you had. The page reloads when done, usually in under a minute.

Run the install script again. It detects the existing panel and only pulls the new release:

curl -sSL https://get.opsvibes.com | sudo sh
docker pull ghcr.io/opsvibes/opsvibes:latest
docker rm -f opsvibes
docker run -d --name opsvibes --network opsvibes \
  --restart unless-stopped \
  -p 3000:3000 \
  -v /etc/opsvibes:/etc/opsvibes \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v /proc:/host/proc:ro \
  -e OPSVIBES_HOST_PROC=/host/proc \
  ghcr.io/opsvibes/opsvibes:latest

Full backup

In the panel, go to Backups → Full backup. A single .vpbak file holds everything needed to rebuild: panel configuration (projects, services, environment variables, accounts), database data, service data and source code uploaded as archives. Code from GitHub is not stored; the panel clones it again.

The file is encrypted with a passphrase and can be pushed daily to S3-compatible storage (R2, B2, Wasabi, MinIO…) or Google Drive.

Keep the passphrase somewhere other than the server. Without it the backup cannot be decrypted, even if you still have the file.

Moving to a new server

  1. Download the .vpbak fileGet the latest full backup from the Backups page, S3 or Google Drive.
  2. Install OpsVibes on the new serverFollow Installation, but do not create an account yet.
  3. Restore from the first screenOn the setup screen, choose Restore from a full backup (.vpbak), upload the file and enter the passphrase and setup token. The panel restarts, rebuilds databases and data, and redeploys every service. Sign in with the account from the backup.
  4. Update DNSPoint your domains' A records to the new server IP.

Only moving one website to another host? Use Project backups on the project page to download a portable copy with the database and the live source code.

Uninstalling

# Stop the panel and its proxy
docker rm -f opsvibes opsvibes-traefik
docker network rm opsvibes

# Optional: delete all panel data (database, secret key, backups)
sudo rm -rf /etc/opsvibes

This only removes the panel. Containers for the apps and databases you deployed keep running. Delete them in the panel first, or find and remove them with docker ps.