TestOps version 5, configuration files for docker compose installation

Configuration sets

1. testops-demo
   1. cannot be used for the production deploy
2. testops
3. testops-ldap
4. testops-saml

testops-demo

Config testops-demo cannot be used as production deployment. Use this as a proof of concept or demo for the decision making.

Demo config contains all the components required for the starting TestOps up, however, this configuration requires a lot of maintenance and will lead to significant downtime and possible data loss when database upgrade is required.

We won't be able to help with data restoration or performance issues when TestOps is deployed with demo config.

testops

Use this configuration if you are going to manage end users and their authentication via TestOps UI (so-called local users or system authentication).

Target deployment architecture

Component	Deployed as
TestOps	via docker compose
Postgres	standalone server
RabbitMQ	preferably standalone server
Redis	preferably standalone server
S3 solution	standalone server

testops-ldap

Use this configuration if you are going to manage end users and their authentication via existing LDAP server.

Target deployment architecture

Component	Deployed as
TestOps	via docker compose
Postgres	standalone server
RabbitMQ	standalone server
Redis	preferably standalone server
S3 solution	standalone server

testops-saml

Use this configuration if you are going to manage end users and their authentication via existing Identity Provider service supporting SAML2 authentication.

Target deployment architecture

Component	Deployed as
TestOps	via docker compose
Postgres	standalone server
RabbitMQ	preferably standalone server
Redis	preferably standalone server
S3 solution	standalone server

testops-openid

Use this configuration if you are going to manage end users and their authentication via existing Identity Provider service supporting OpenID authentication.

Target deployment architecture

Component	Deployed as
TestOps	via docker compose
Postgres	standalone server
RabbitMQ	preferably standalone server
Redis	preferably standalone server
S3 solution	standalone server

Configuration validation

GitHub Actions validates all testops*/docker-compose.yml files on pushes to main and pull requests using docker compose config --quiet and each configuration's env-example. This checks YAML syntax and the Compose model without pulling images or starting containers.

To validate a configuration locally, run from the repository root:

docker compose --env-file testops/env-example -f testops/docker-compose.yml config --quiet

Upgrade from version 4 to version 5

The only available paths from to upgrade 4 to 5 are

• 4.25.1 → 5.3.3, then to next available version
• 4.26.1 → 5.3.3 then to next available version

Upgrade process is thoroughly described in TestOps documentation here.