blackbeard420/kore
1
0
Fork 0
mirror of https://github.com/jorisvink/kore synced 2025-03-09 04:29:02 -04:00
Code Issues Projects Releases Wiki Activity

Add logfile to example configuration

Browse Source
This commit is contained in:
Joris Vink 2022-03-15 19:37:17 +01:00
parent 8689df70d9
commit f9c3fac6fa
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
conf/kore.conf.example
View File

@ -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.