Snow Owl AP
GitHubNeed Help?
  • ℹ️Introduction
    • Snow Owl® AP Admin Guide
  • 🗺️Plan your deployment
    • Technology stack
    • Hardware requirements
    • Software requirements
  • 📤Configuration
    • Release package
    • Folder structure
    • Get SSL certificate (optional)
    • Preload dataset (optional)
    • Configure Elastic Cloud (optional)
    • Spin up the service
  • ↗️Software Upgrades
    • Perform an upgrade
  • 💾Backup and Restore
    • Backup
    • Restore
  • 📋Miscellaneous
    • User management
    • Install the client
Powered by GitBook
On this page
Export as PDF
  1. Software Upgrades

Perform an upgrade

PreviousSpin up the serviceNextBackup

Last updated 3 years ago

When a new Snow Owl Authoring Platform release is available we recommend performing the following steps.

New releases are going to be distributed the same way: a docker stack and its configuration within an archive.

It is advised to decompress the new release files to a temporary folder and compare the contents of ./snow-owl/docker .

[root@host]# diff /opt/snow-owl/docker/ /opt/new-snow-owl-release/snow-owl/docker/
Common subdirectories: /opt/snow-owl/docker/configs and /opt/new-snow-owl-release/snow-owl/docker/configs
diff /opt/snow-owl/docker/.env /opt/new-snow-owl-release/snow-owl/docker/.env
10c10
< ELASTICSEARCH_VERSION=7.12.0
---
> ELASTICSEARCH_VERSION=7.16.3
24c24
< SNOWOWL_VERSION=7.18.0
---
> SNOWOWL_VERSION=7.19.0

The changes usually are restricted to version numbers in the .env file. In such cases, it is equally acceptable to overwrite the contents of the ./snow-owl/docker folder as is or cherry-pick the necessary modifications by hand.

Once the new version of the files is in place it is sufficient to just issue the following commands, an explicit stop of the service is not even required (in the folder ./snow-owl/docker):

docker-compose pull
docker-compose up -d

Do not usedocker-compose restart because it won't pick up any .yml or .env file changes. See the .

↗️
official docker guider