- testops-demo
- cannot be used for the production deploy
- testops
- testops-ldap
- testops-saml
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.
Use this configuration if you are going to manage end users and their authentication via TestOps UI (so-called local users or system authentication).
Component | Deployed as |
---|---|
TestOps | via docker compose |
Postgres | standalone server |
RabbitMQ | preferably standalone server |
Redis | preferably standalone server |
S3 solution | standalone server |
Use this configuration if you are going to manage end users and their authentication via existing LDAP server.
Component | Deployed as |
---|---|
TestOps | via docker compose |
Postgres | standalone server |
RabbitMQ | standalone server |
Redis | preferably standalone server |
S3 solution | standalone server |
Use this configuration if you are going to manage end users and their authentication via existing Identity Provider service supporting SAML2 authentication.
Component | Deployed as |
---|---|
TestOps | via docker compose |
Postgres | standalone server |
RabbitMQ | preferably standalone server |
Redis | preferably standalone server |
S3 solution | standalone server |
Use this configuration if you are going to manage end users and their authentication via existing Identity Provider service supporting OpenID authentication.
Component | Deployed as |
---|---|
TestOps | via docker compose |
Postgres | standalone server |
RabbitMQ | preferably standalone server |
Redis | preferably standalone server |
S3 solution | standalone server |
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.