Updating
Each Staaash release is built for one exact version of the app. To update, you point your install at the new version and restart it.
Before you update
Section titled “Before you update”- Make a backup of the files and the database. Follow Backup and Restore. Do not skip this step.
- Read the notes of the new release on the releases page, or in the app’s update notice. Read ⚠️ Upgrade notes closely. It says when the release changes the database, the compose file or
example.env. If you skip releases, read the upgrade notes of each one. - Check that the admin Overview shows no problems. See Admin Guide.
Alpha and beta releases of Staaash cannot be updated to 2.0. Start a fresh install of the current version and move your files in through the app. Do not point it at the old database or storage folders.
Staaash shows a notice in the app when a new version exists. Admins can also press Check now on the Overview screen.
Update
Section titled “Update”-
Find the tag of the new release, for example
vX.Y.Z. It is the title of the release. -
Open your
.envfile and setSTAAASH_VERSIONto that tag:STAAASH_VERSION=vX.Y.Z -
Download the new
docker-compose.ymlfrom the release Assets and replace your old one. If you use HTTPS from Reverse Proxy, replacecompose.https.ymlandCaddyfiletoo. Keep your.envfile. -
Pull the new images and restart:
docker compose pulldocker compose up -d
Staaash updates its own database when it starts. Give it a minute.
On the Windows server installer, run the newer installer instead. See Windows Server.
Check that it worked
Section titled “Check that it worked”- Open Staaash and sign in.
- Open the admin Overview. The version number should be the new one, and every health line should be green. Restore check is gray when it has never run. That is fine, but after an update it is a good extra check: open admin Jobs and run Restore check. It should finish without issues.
- Open a few files, and upload a small one.
If something goes wrong
Section titled “If something goes wrong”Your old data is safe in your backup. Do not delete the backup until the new version has run well for a few days.
To go back to the old version, you restore the backup you made before the update. Set STAAASH_VERSION back to the old tag too.
Read Troubleshooting if the app does not start after an update.
Release candidates
Section titled “Release candidates”A release marked “Pre-release” is a release candidate. It is for testing the next version. In admin Settings, under Updates, the Channel option controls which releases the update notice follows: Automatic, Stable or Release candidates. Leave it on Automatic or Stable unless you want to test.