Service Update

Note

If you need to make a major version update, from version 1.x to version 2.x for example, please consult the Major Version Migration

The update depends on your setup and SEB Serverversion change. If you change from one major version to another, please consult the migration guide for the major version upgrade specifically. Please be aware that if you have adapted a specified setup for your needs you need to also adapt the following update procedure.

To update an already installed and bundled SEB Server service, follow the steps below:

  1. Shout down the SEB Server setup docker services with

$ docker-compose down

  1. Update to the newest or preferred version within the seb-server-setup. Use git tags to show the available tags. If there are already local changed - if the configuration was modified from the original settings, and the local changes shall still be used and remain, git stash can be used to locally store and merge them.

# Get new tags from remote
$ git fetch --tags

# Get latest tag name
$ latestTag=$(git describe --tags `git rev-list --tags --max-count=1`)

# If local changes shall remain
$ git stash

# Checkout latest tag
$ git checkout $latestTag

# If local changes shall remain
$ git stash apply

Note

Usually you want to point to the exact version of the SEB Server setup by using semantic versioning like 1.0.0 or 1.0.1. You are also able to set the latest minor version to always get the latest specific minor version with all patches. If you want the latest minor version use version tags like 1.0-latest or 1.1-latest.

  1. Do some additional configuration if needed.

Note

Since SEB Server version 1.2.x there is a new setup procedure (dockerhub). If you use this setup, you have to provide the passwords that was given on startup again. Do not use another password for the SEBSERVER_PWD and only adapt the DB_SA_PWD if your database has a new password for the user. You can just copy or recreate the .env in the working directory that contains the needed password or you can give them with the docker-compose up command later on.

  1. Rebuild the image with the new SEB Server version

$ docker-compose build --no-cache

Or with a pull if you use a setup with an image from docker-hub:

$ docker-compose pull

  1. Boot the SEB Server setup docker services with

$ docker-compose up -d

  1. Check if the containers are started and running and everything is set in place for the particular setup

$ docker ps --all
$ docker logs ${container name}

  1. Cleanup the docker engine with

$ docker system prune