challenger

OAuth 2.0-based authentication service that validates user can receive messages at a certain address
Log | Files | Refs | Submodules | README | LICENSE
commit 9a7b2c846f886216c3c83a7802026ffa77fc048e
parent 1e053baabd72815b8f28401089a08aad3b59a924
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Fri, 15 Dec 2023 16:37:58 +0800

use sane default for DB name

Diffstat:

Mdebian/etc/challenger/secrets/challenger-db-secret.conf | 2+-


1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/etc/challenger/secrets/challenger-db-secret.conf b/debian/etc/challenger/secrets/challenger-db-secret.conf
@@ -2,7 +2,7 @@
 
 # Typically, there should only be a single line here, of the form:
 
-CONFIG=postgres:///DATABASE
+CONFIG=postgres:///challenger
 
 # The details of the URI depend on where the database lives and how
 # access control was configured.