-
Notifications
You must be signed in to change notification settings - Fork 5
/
.env.example
136 lines (100 loc) · 4.59 KB
/
.env.example
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
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
##########################################
# Murdock backend application parameters
##########################################
## External port exposed
MURDOCK_PORT=8000
## External API port if exposed
MURDOCK_API_PORT=8001
## External base url used to reach the Murdock UI/API
MURDOCK_BASE_URL=http://localhost:8000
## External url used to reach the websocket live updates on job status
MURDOCK_WS_URL=ws://localhost:8000/ws/status
## Directory on disk where jobs results and outputs are stored
MURDOCK_WORK_DIR=/tmp/murdock-data
## Directory containing the murdock scripts
MURDOCK_SCRIPTS_DIR=./scripts
## Name of the script used to run a Murdock job
MURDOCK_SCRIPT_NAME=run.sh
## List of github events supported, by default support pull_request and push
## events (the murdock doesn't support more)
MURDOCK_ACCEPTED_EVENTS=["pull_request", "push"]
## Number of parallel workers
MURDOCK_NUM_WORKERS=1
## Additional custom environment variables
# MURDOCK_CUSTOM_ENV={"SOME_ENV": "some value"}
## Set this to 1 to receive notification on job completion. Supported notifiers
## are email and Matrix. See murdock.config.py for the list of configuration
## options related to each notifiers.
MURDOCK_NOTIFIER_ENABLE=0
## Github label that must be set to handle a pull request event or start a pull
## request job
CI_READY_LABEL=CI: ready for build
## List of Github labels to allow some jobs to be processed in priority (e.g. fasttracked)
CI_FASTTRACK_LABELS=["CI: skip compile test", "Process: release backport"]
##################################
# Murdock database configuration
##################################
## Database backend type, supported "mongodb" and "postgresql"
MURDOCK_DB_TYPE=mongodb
## Directory containing the Mongo database files
MONGODB_BD_DATA_DIR=/tmp/mongodb
## Murdock database hostname
MURDOCK_DB_HOST=localhost
## Murdock database port, 0 for type default
MURDOCK_DB_PORT=0
## Name of the Mongo database
MURDOCK_DB_NAME=murdock
## Murdock database auth user
MURDOCK_DB_AUTH_USER=murdock
## Murdock database auth password
MURDOCK_DB_AUTH_PASSWORD=hunter2
#################################
# Github integration parameters
#################################
## Github Oauth client ID and secret
MURDOCK_GITHUB_APP_CLIENT_ID=
MURDOCK_GITHUB_APP_CLIENT_SECRET=
## Github repository name (orga/name)
GITHUB_REPO=
## Secret used to decrypt the webhook payload received on PR/push events
GITHUB_WEBHOOK_SECRET=
## Token of the account used to interact with the Github REST API
## (used for setting the commit status, post comment on PRs, etc)
GITHUB_API_TOKEN=
#########################################
# Docker deployment specific parameters
#########################################
## Docker compose project name. This is used to differenciate container names. If
## running multiple instances for different Murdock projects, make sure to also
## use different values for MURDOCK_DOCKER_NETWORK (see setting below) in your
## different project .env files.
## The MURDOCK_PORT (see first parameter of this file) must also be different.
COMPOSE_PROJECT_NAME=default
## Docker network on which containers (murdock-api, murdock-frontend, mongo,
## proxy) are running
MURDOCK_DOCKER_NETWORK=default
## Specify the host directory where result data are located when running the
## murdock job in its own Docker container (e.g when MURDOCK_RUN_IN_DOCKER=1)
MURDOCK_HOST_WORK_DIR=/tmp/murdock-data
## If running in Docker, specify the default Docker image used to run job tasks
MURDOCK_DOCKER_DEFAULT_TASK_IMAGE=murdockng/murdock-scripts-example
# Dictionnary containing extra Docker volumes required by the container running
# the murdock script. Example:
# MURDOCK_DOCKER_VOLUMES={"/tmp/cacheonhost": "/cacheindocker"}
## User UID/GID used to run the Murdock services. If using a different value,
## the Docker image of the murdock service must be rebuilt
MURDOCK_USER_UID=1000
MURDOCK_USER_GID=1000
## GID of the docker group on the host. The user above must belong to this group
## if MURDOCK_RUN_IN_DOCKER=1 so the container running the Murdock API can
## spawn the job Docker container using the Docker service running on the host.
## The value below might differ depending on the system but can be retrieved
## using "cut -d: -f3 < <(getent group docker)"
MURDOCK_DOCKER_GID=130
## Directory containing the murdock-html code (reactjs application) and which
## should contain a build directory
MURDOCK_HTML_DIR=./murdock-html
## uvicorn access log logging level. Controls logging of endpoint access. These
## are logged at INFO level. Anything above suppresses logging of the individual
## endpoint access requests by clients.
UVICORN_LOG_LEVEL=info