We were hoping to collect some statistics from the requests that came in. I did not want to add those details in the Caddyfile because I din’t want to clutter the file with information that is not related to configuring different directives. Maybe writing it to a different file that can be read when caddy starts up might not be a bad idea.
Is there a graceful way to restart caddy outside of killing the current process? Currently we do
ExecReload=/bin/kill -USR1 $MAINPID for a reload.
We are currently running a slightly newer version than 0.11.0, specific commit id being: d3b731e9255b72d4571a5aac125634cf1b6031dc.