BucketDeskWorkspaceStart free trial

Platform teams

Upgrading

This page is for self-hosted installs. On the hosted service at app.bucketdesk.com there is nothing to upgrade: releases are applied for you, and the release notes say what changed.

How releases work#

  • Every release, including security fixes, is published to the public image and the install kit on the day it ships.
  • Updating does not need a licence. An install whose licence has lapsed can still update.
  • Each kit pins one release. The kit’s compose.yaml names the image version, a tag made of the release date and a build ID, such as 20261112-442fdaa9.
  • Release notes are at app.bucketdesk.com/release-notes.

Before you upgrade#

  • Read the release notes for the versions between yours and the new one.
  • Take a snapshot or backup of the server, including its Docker volumes. The database lives on the server, and database changes run when the new version starts.
  • Keep a copy of .env, aws/ and certs/. The kit does not contain them, so unzipping a new kit does not overwrite them.
  • Pick a quiet time. The app is briefly unavailable while the containers restart.

Upgrade#

  1. Download the new kit.
  2. Unzip it over the install folder.
  3. Pull the new images and restart:
bash, in the install folder
docker compose pull && docker compose up -d

Database changes run automatically when the app starts.

On the AWS install

Open a shell with Systems Manager Session Manager. The install folder is /opt/bucketdesk, and the stack is started with two Compose files, so name both:

bash, in /opt/bucketdesk
docker compose -f compose.yaml -f ec2/compose.ec2.yaml pull
docker compose -f compose.yaml -f ec2/compose.ec2.yaml up -d

NoteIf you turned office previews on for an AWS install, you start it with compose.yaml alone, so use the plain command above instead.

After an upgrade#

Sign in and open a file. Then check whether the release notes ask for either of these.

Update a connection’s stack

When a release changes the permissions a connection needs, the connection shows a message that the deployed stack is from another release. Open the connection, follow its update link, and submit the stack update in AWS. Until then, features that depend on the new permissions fail on that connection.

Update the AWS access stack

When a release changes aws-access.yaml, update that stack with the new template from the kit, then run its CredentialsFileCommand output again in the install folder to rewrite the credentials files.

If something goes wrong#

  • Look at the newest files in logs/ in the install folder, and at docker compose ps to see which container is not running.
  • Because database changes run on start, going back to an older release means restoring the snapshot you took before upgrading, not only starting the old images.
  • Email info@bucketdesk.com with the most recent log files and the version you upgraded from and to.

Renewing a licence#

A licence renewal is not an upgrade and needs no restart. The owner pastes the renewed key under Settings → Licence and it applies at once. After a paid licence expires everything keeps working for 30 days, then the install falls back to the free plan until a renewed key is pasted.

Settings, Licence on a self-hosted install: a banner saying the licence expired, a status panel marked Expired that explains the free plan, and buttons to request an invoice or get a licence
ScreenSettings → Licence once the first 30 days have ended with no key pasted: the install runs on the free plan.

Something wrong or missing on this page? Email info@bucketdesk.com. Last updated November 12, 2026.

Let's chat

Questions? Message directly.