challenger

OAuth 2.0-based authentication service that validates user can receive messages at a certain address
Log | Files | Refs | Submodules | README | LICENSE

commit 196178e8103ca8630bc128f15cbdde63839e0edb
parent 327c46efb5adca2dfb9705601ef213b248471a49
Author: Florian Dold <florian@dold.me>
Date:   Fri, 23 Aug 2024 16:12:58 +0200

debian: challenger config paths

Diffstat:
Mdebian/etc/challenger/challenger.conf | 8++++++++
1 file changed, 8 insertions(+), 0 deletions(-)

diff --git a/debian/etc/challenger/challenger.conf b/debian/etc/challenger/challenger.conf @@ -10,6 +10,14 @@ SERVE = unix # if left empty. Only used if "SERVE" is 'tcp'. # BIND_TO = + +[paths] +CHALLENGER_HOME = /var/lib/challenger +CHALLENGER_RUNTIME_DIR = /run/challenger +CHALLENGER_CONFIG_HOME = /etc/challenger +CHALLENGER_DATA_HOME = /var/lib/challenger +CHALLENGER_CACHE_HOME = /var/cache/challenger + # Load DB configuration from secret file, only accessible to some users @inline-secret@ challengerdb-postgres secrets/challenger-db.secret.conf