--- valkey.conf.orig	2025-03-31 19:55:59 UTC
+++ valkey.conf
@@ -353,7 +353,7 @@ tcp-keepalive 300
 # By default the server does not run as a daemon. Use 'yes' if you need it.
 # Note that the server will write a pid file in /var/run/valkey.pid when daemonized.
 # When the server is supervised by upstart or systemd, this parameter has no impact.
-daemonize no
+daemonize yes
 
 # If you run the server from upstart or systemd, the server can interact with your
 # supervision tree. Options:
@@ -385,7 +385,7 @@ daemonize no
 #
 # Note that on modern Linux systems "/run/valkey.pid" is more conforming
 # and should be used instead.
-pidfile /var/run/valkey_6379.pid
+pidfile %%VALKEY_RUNDIR%%/valkey.pid
 
 # Specify the server verbosity level.
 # This can be one of:
@@ -416,7 +416,7 @@ loglevel notice
 # Specify the log file name. Also the empty string can be used to force
 # the server to log on the standard output. Note that if you use standard
 # output for logging but daemonize, logs will be sent to /dev/null
-logfile ""
+logfile %%VALKEY_LOGDIR%%/valkey.log
 
 # To enable logging to the system logger, just set 'syslog-enabled' to yes,
 # and optionally update the other syslog parameters to suit your needs.
@@ -606,7 +606,7 @@ rdb-del-sync-files no
 # Note that modifying 'dir' during runtime may have unexpected behavior,
 # for example when a child process is running, related file operations may
 # have unexpected effects.
-dir ./
+dir %%VALKEY_DBDIR%%/
 
 ################################# REPLICATION #################################