challenger

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

commit 9a761b9a7cbed45c10d20bdc33f5e5d5ffdf4274
parent a756312edc644610246e005176a0816a3e486980
Author: Florian Dold <florian@dold.me>
Date:   Fri, 23 Aug 2024 16:32:37 +0200

debian: paths

Diffstat:
Mdebian/challenger-httpd.tmpfiles | 5+++--
Msrc/challenger/challenger.conf | 2+-
2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/debian/challenger-httpd.tmpfiles b/debian/challenger-httpd.tmpfiles @@ -1,2 +1,3 @@ -#Type Path Mode UID GID Age Argument -d /run/challenger 0755 root root - - +#Type Path Mode UID GID Age Argument +d /run/challenger 0755 root root - - +d /run/challenger/httpd 0750 challenger-httpd www-data - - diff --git a/src/challenger/challenger.conf b/src/challenger/challenger.conf @@ -17,7 +17,7 @@ PORT = 9967 # BIND_TO = # Which unix domain path should we bind to? Only used if "SERVE" is 'unix'. -UNIXPATH = ${CHALLENGER_RUNTIME_DIR}/challenger.http +UNIXPATH = ${CHALLENGER_RUNTIME_DIR}/httpd/challenger.http # What should be the file access permissions (see chmod) for "UNIXPATH"? UNIXPATH_MODE = 660