1
+ # Templated passwords as `{some-strong-password}` are written to make sure our
2
+ # script detects those, if you manually change those the `{}` are not required and
3
+ # would become part of the password.
4
+ # Adding `strong` in the template will create longer passwords and is used for the
5
+ # passwords which almost never need to be manually typed.
6
+
1
7
# Password for the MySQL replication user.
2
8
# Set this to enable master-master replication between two domservers.
3
- #REPLICATION_PASSWORD: some-replication-password
9
+ #REPLICATION_PASSWORD: { some-strong- replication-password}
4
10
5
11
# Database user password.
6
- DB_PASSWORD: some-database-password
12
+ DB_PASSWORD: { some-strong- database-password}
7
13
8
14
# Credentials for the judgehost.
9
15
JUDGEHOST_USER: judgehost
10
- JUDGEHOST_PASSWORD: some-judgehost-password
16
+ JUDGEHOST_PASSWORD: { some-strong- judgehost-password}
11
17
12
18
# Username and password to be used in .netrc files on admin machines
13
19
ADMIN_USER: admin
14
- ADMIN_PASSWORD: some-admin-password
20
+ ADMIN_PASSWORD: { some-admin-password}
15
21
16
22
# Password for domjudge shell user
17
23
# Set this to enable a password on the 'domjudge' shell accounts
18
24
# created on the domserver and judgehosts.
19
- #DJ_SHELL_USER_PW: some-hashed-password
25
+ #DJ_SHELL_USER_PW: { some-hashed-password}
20
26
21
27
# Accounts to create when setting up the CDS
22
28
CDS_ACCOUNTS:
23
29
- username: admin
24
- password: adm1n
30
+ password: {some- adm1n-password}
25
31
type: admin
26
32
- username: presAdmin
27
- password: padm1n
33
+ password: {some-presentation-adm1n-password}
28
34
type: admin
29
35
- username: blue
30
36
password: blu3
@@ -36,7 +42,7 @@ CDS_ACCOUNTS:
36
42
password: publ1c
37
43
type: public
38
44
- username: presentation
39
- password: presentat1on
45
+ password: {some-public-presentation-password}
40
46
type: public
41
47
- username: myicpc
42
48
password: my1cpc
0 commit comments