forked from qameta/allure-docker-compose
-
Notifications
You must be signed in to change notification settings - Fork 0
/
env-example-external-s3
83 lines (70 loc) · 2.09 KB
/
env-example-external-s3
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
#Allure TestOps release management
ALLURE_VERSION=4.5.0
#The port to access Allure TestOps' UI
ALLURE_INSTANCE_PORT=8080
TZ="Europe/Moscow"
# Standard Login Admin
ALLURE_ADMIN=admin
#update before going to production
ALLURE_ADMIN_PASS=admin
# Crypto
ALLURE_JWT_SECRET=<SET_YOUR_SECRET_HERE>
ALLURE_CRYPTO_PASSWORD=<SET_YOUR_PASSWORD_HERE>
# TLS
ALLURE_SECURE_COOKIE=false
ALLURE_CERTIFICATE="./certs/fullchain.pem"
ALLURE_KEY="./certs/privkey.pem"
# Registry Settings
ALLURE_REGISTRY=docker.io
ALLURE_SLUG=allure
# External Network Settings
ALLURE_HOST=allure.io
ALLURE_PROTO=http
ALLURE_SESSION_DURATION=57600
# Service Discovery
CONSUL_HOST=localhost
CONSUL_PORT=8500
CONSUL_SCHEME=http
# Gateway
ALLURE_GATEWAY_PORT=8080
ALLURE_REDIS_HOST=redis
ALLURE_REDIS_PORT=6379
ALLURE_REDIS_PASS=Y5ZBqrcb68WKA9ZZ
# UAA
ALLURE_UAA_SERVICE_NAME=allure-uaa-service
ALLURE_UAA_CONTEXT_PATH=/uaa
ALLURE_UAA_DB_HOST=uaa-db
ALLURE_UAA_DB_NAME=uaa
ALLURE_UAA_DB_USERNAME=uaa
ALLURE_UAA_DB_PASS=CjAXjUav3eh3cmWk
ALLURE_UAA_PORT=8082
ALLURE_UAA_DB_PORT=5432
#UAA user registration management
ALLURE_REGISTRATION_AUTOAPPROVE=false
ALLURE_REGISTRATION_ENABLED=false
ALLURE_REGISTRATION_DEFAULT_ROLE=ROLE_AUDITOR
# Report
ALLURE_REPORT_SERVICE_NAME=allure-report-service
ALLURE_REPORT_CONTEXT_PATH=/rs
ALLURE_REPORT_DB_HOST=report-db
ALLURE_REPORT_DB_NAME=report
ALLURE_REPORT_DB_USERNAME=report
ALLURE_REPORT_DB_PASS=GnNc9QQcLzZfhVNn
ALLURE_REPORT_PORT=8081
ALLURE_REPORT_DB_PORT=5432
ALLURE_RABBIT_HOST=rabbitmq
ALLURE_RABBIT_PORT=5672
ALLURE_RABBIT_USER=allure
ALLURE_RABBIT_PASS=wNaxbX7wEhqA6ZDQ
# S3
# This variable is responsible for proxy S3 type (azure - for microsoft Azure, gcs - Google Cloud, s3 - for the rest of providers)
ALLURE_S3_PROVIDER=s3
ALLURE_S3_MINIO_URL=http://minio-proxy:9000
ALLURE_S3_URL=https://<your_S3_provider_API_endpoint_here>
ALLURE_S3_BUCKET=allure-testops
ALLURE_S3_REGION=fra1
ALLURE_S3_ACCESS_KEY=<your_access_key>
ALLURE_S3_SECRET_KEY=<your_secret_key>
# Do not change it, because it's Minio's parameter, not external S3's
ALLURE_S3_SECRET_PATHSTYLE=true
RABBIT_ERLANG_COOKIE=fTwP5LxRVjZ9XJkyWmJSKR5hPDWMjkQx