kore

An easy to use, scalable and secure web application framework for writing web APIs in C.
Commits | Files | Refs | README | LICENSE | git clone https://git.kore.io/kore.git

commit f9c3fac6fa47a09ea76e7d541d6f0570b61d32dc
parent 8689df70d9c0dfd68389e1a5934734a2bc5bd525
Author: Joris Vink <joris@coders.se>
Date:   Tue, 15 Mar 2022 19:37:17 +0100

Add logfile to example configuration

Diffstat:
conf/kore.conf.example | 15++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/conf/kore.conf.example b/conf/kore.conf.example @@ -23,12 +23,12 @@ server tls { # Kore can have multiple settings for each processes that run under it. # There are 3 different type of processes: # -# 1) Worker processes, these handle the HTTP requests and your code +# 1) A worker process, these handle the HTTP requests and your code # runs inside of these. -# 2) The keymgr process, this handles your domain private keys +# 2) A keymgr process, this handles your domain private keys # and signing during the TLS handshakes. It also holds your # ACME account-key and will sign ACME requests. -# 3) The acme process, this talks to the ACME servers. +# 3) An acme process, this talks to the ACME servers. # # You can individually turn on/off chrooting and dropping user # privileges per process. The -n and -r command-line options @@ -72,6 +72,15 @@ privsep keymgr { root /etc/keymgr } +# Configure Kore to log all worker output to a certain file. +# +# This forces all logs from the workers to be written to this file +# instead of stdout. Note that this is not the actual access log. +# +# Any message logged by your application with kore_log() will also +# appear under here. +#logfile /var/log/kore.log + # How many worker processes Kore will spawn. If the directive # worker_set_affinity is set to 1 (the default) Kore will automatically # pin these worker processes to different CPU cores in your system.