Use documentation pages instead
Old compose repo is deprecated and moved to Legacy do not use it. Please.
- 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
- Install RabbitMQ on SEPARATE Server.
- Install Minio on SEPARATE Server. (If you have AWS S3 or Ceph, skip this step)
- Install Docker:
curl -fsSL https://get.docker.com -o get-docker.sh
chmod +x get-docker.sh
./get-docker.sh
mkdir -p /opt/allure-testops
cp testops/docker-compose.yml /opt/allure-testops/
cp testops/env-example /opt/allure-testops/.env
- Edit
/opt/allure-testops/.env
with your favourite text editor. cd /opt/allure-testops/
docker compose up -d
- 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
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.
- Install Docker:
curl -fsSL https://get.docker.com -o get-docker.sh
chmod +x get-docker.sh
./get-docker.sh
mkdir -p /opt/allure-testops
cp testops-demo/docker-compose.yml /opt/allure-testops/
cp testops-demo/env-example /opt/allure-testops/.env
- Edit
/opt/allure-testops/.env
with your favourite text editor. cd /opt/allure-testops/
docker compose up -d
- Set your LoadBalancer to proxy traffic to 8080 port (Gateway)
This may help you to migrate to production grade deployment
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_".
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