Skip to main content

Upgrading connectCenter

Upgrading a Docker-based connectCenter deployment is simple: back up, change the image tag, restart. The backend applies any database schema changes automatically on startup via Flyway — you do not apply anything to the database yourself.

Always back up first

An upgrade changes your database schema in place. Take a full backup before you start and verify it can be restored — it is your only way back if something goes wrong. See Backup and Restore.

Upgrade steps​

  1. Back up your database — see Backup and Restore.

  2. Change the image tags in your docker-compose.yml to the target version. The three oagi1docker/srt-* images are released together, so set all three to the same tag:

    services:
      frontend:
        image: oagi1docker/srt-web:3.5.2
      backend:
        image: oagi1docker/srt-http-gateway:3.5.2
      db:
        image: oagi1docker/srt-repo:3.5.2

    Leave the redis image and your named volumes unchanged so the new containers attach to your existing data.

  3. Pull and restart (use the Docker Compose v2 plugin — docker compose, two words):

    docker compose pull
    docker compose up -d

    On startup the backend runs its bundled Flyway migrations and brings the schema up to date. There is nothing else to run.

  4. Verify. Tail the backend logs for a clean start, then sign in and confirm your releases, code lists, and BIE packages are present and that a representative export (XML / JSON / OpenAPI) still generates.

    docker compose logs -f backend

Rollback​

If the upgrade fails, restore the database from the backup you took in step 1, revert the image tags in docker-compose.yml to the previous version, and run docker compose up -d.