challenger

OAuth 2.0-based authentication service that validates user can receive messages at a certain address
Log | Files | Refs | Submodules | README | LICENSE
commit 241f0d827c97f40727692cd8af4248ca3d7b0c6a
parent 4c2ebdb4434177e1a35d9dba8f7d82da48e3d047
Author: Florian Dold <florian@dold.me>
Date:   Fri, 23 Aug 2024 15:37:26 +0200

debian: config filename

Diffstat:

Mdebian/etc/challenger/challenger.conf | 2+-


Rdebian/etc/challenger/secrets/challenger-db-secret.conf -> debian/etc/challenger/secrets/challenger-db.secret.conf | 0


2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/etc/challenger/challenger.conf b/debian/etc/challenger/challenger.conf
@@ -10,9 +10,9 @@ SERVE = unix
 # if left empty.  Only used if "SERVE" is 'tcp'.
 # BIND_TO =
 
+# Load DB configuration from secret file, only accessible to some users
 @inline-secret@ challengerdb-postgres secrets/challenger-db.secret.conf
 
-
 # Inline configuration files from conf.d
 @inline-matching@ conf.d/*.conf
 
diff --git a/debian/etc/challenger/secrets/challenger-db-secret.conf b/debian/etc/challenger/secrets/challenger-db.secret.conf