Skip to content
This repository has been archived by the owner on Sep 27, 2024. It is now read-only.

Docker Compose reference deployment

Notifications You must be signed in to change notification settings

qameta/allure-docker-compose

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

This repository is OUTDATED and mustn't be used for the deployment of Allure TestOps

Use documentation pages instead

Docker Compose Deployment

Old compose repo is deprecated and moved to Legacy do not use it. Please.

schema

For Fresh Production Install

  1. Get 2 Postgres (ver >= 12) databases for uaa and report (NOT ON THE SAME SERVER with TESTOPS). You can get SAAS Databases from your cloud provider. Amazon AuroraDB is also supported. If you have everything self-hosted, get one from Official Postgres Vendor
  2. Install RabbitMQ on SEPARATE Server.
  3. Install Minio on SEPARATE Server. (If you have AWS S3 or Ceph, skip this step)
  4. Install Docker:
curl -fsSL https://get.docker.com -o get-docker.sh
chmod +x get-docker.sh
./get-docker.sh
  1. mkdir -p /opt/allure-testops
  2. cp testops/docker-compose.yml /opt/allure-testops/
  3. cp testops/env-example /opt/allure-testops/.env
  4. Edit /opt/allure-testops/.env with your favourite text editor.
  5. cd /opt/allure-testops/
  6. docker compose up -d
  7. Set your LoadBalancer to proxy traffic to 8080 port (Gateway)

If you want TestOps to use SSO, copy testops-{auth} instead on steps 6-7, for example NOT testops but testops-ldap For ENV reference please watch References

For Fresh Demo Install

This Kind of installation is NOT PRODUCTION GRADE. Use it only for testing. In case you lose data, please don't blame us. There is nothing we can do in this case.

  1. Install Docker:
curl -fsSL https://get.docker.com -o get-docker.sh
chmod +x get-docker.sh
./get-docker.sh
  1. mkdir -p /opt/allure-testops
  2. cp testops-demo/docker-compose.yml /opt/allure-testops/
  3. cp testops-demo/env-example /opt/allure-testops/.env
  4. Edit /opt/allure-testops/.env with your favourite text editor.
  5. cd /opt/allure-testops/
  6. docker compose up -d
  7. Set your LoadBalancer to proxy traffic to 8080 port (Gateway)

Lego Approach

This may help you to migrate to production grade deployment

Release notes

2023-06-13 We have added SMTP integration parameters for adding new members and password reset functionality.

To enable Allure TestOps to send email notifications to new team members and for password reset, you need to add environment variables to the UAA service settings.

The environment variables for SMTP configuration in Allure TestOps are named with the prefix "SPRING_MAIL_".

2022-11-03 For forthcoming releases we've added ALLURE_JWT_SECRET to allure report, uaa

When using releases after 4.9.2 (excluding it) all the services will require ALLURE_JWT_SECRET to start.

ALLURE_JWT_SECRET should be the same for all the services, i.e. to be set via .env

About

Docker Compose reference deployment

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages