We announce new updates in our news feed here: https://support.deskpro.com/en-US/news/release-announcements

Or alternatively, you can watch for new tagged releases on our docker hub repository page at deskpro/deskpro-product. Onprem versions are always tagged with a -onprem suffix. E.g. 2023.33.0-onprem refers to the onprem build for v2023.33.0.

Updating Deskpro

1. Pull the latest image from docker hub

2. Turn off / disable any running Deskpro containers

3. Perform a database backup

4. Run data migrations using the new image (see below)

5. Restart your Deskpro containers using the new tagged image. (E.g. update your docker-compose.yml with the new version tag).

For example:

# Assign the version you want to an env var
# (this just makes the following commands a bit easier to read)
DPVERSION=2023.31.1

# pull the image you're updating to
docker pull deskpro/deskpro-horizon:$DPVERSION-onprem

# If we started two containers as recommended, stopping them might look something like this:
docker stop deskpro_web deskpro_tasks && docker rm deskpro_web deskpro_tasks

# perform a database backup. You can do this through a Deskpro container which has all of the necessary utilities already:
docker run --rm --env-file="config.env" -v "./db-backup:/db-backup" deskpro/deskpro-horizon:$DPVERSION-onprem \
  exec bash -c "mysqldump-primary --hex-blob --lock-tables=false --single-transaction | gzip > /db-backup/dump.sql.gz"

# Now you need to run database migrations which can be done like this:
docker run --rm --env-file="config.env" -v "./db-backup:/db-backup" deskpro/deskpro-horizon:$DPVERSION-onprem \
  exec tools/migrations/artisan migrations:exec -vvv --run

# Finally, you can re-start the containers you stopped
# (be sure to use the same parameters as you did when starting your existing containers last time)
docker start --name deskpro_web --env-file="config.env" -p 80:80 -d deskpro/deskpro-horizon:$DPVERSION-onprem web
docker start --name deskpro_tasks --env-file="config.env" -d deskpro/deskpro-horizon:$DPVERSION-onprem tasks
 copy

These general steps are the same no matter how you run Deskpro. But if you're using docker-compose, it's slightly easier because the commands to run can be coded directly into your compose file. Refer to our example here: Example: Running Deskpro with Docker Compose