If you made any changes to vhost settings (vhost-gen templates or backend configuration) or to the webserver configuration itself, you can trigger a manual reload of watcherd
here to apply them. No need to restart the Docker Compose stack.
Daemon | Status | Pid | Uptime | Action |
---|---|---|---|---|
watcherd | RUNNING | 531 | 42 | |
httpd | RUNNING | 530 | 42 |
2025/02/10 19:34:08 [notice] 616#616: signal process started
watcherd: [INFO] Starting daemon: 2025-02-10 19:34:08 cert-gen: [INFO] Create CSR file: /etc/httpd/cert/mass/am-log.com.csr cert-gen: [INFO] Create CRT file: /etc/httpd/cert/mass/am-log.com.crt cert-gen: [INFO] Verify CRT file: /etc/httpd/cert/mass/am-log.com.crt cert-gen: [INFO] Verify CRT against CA file: /ca/devilbox-ca.crt [INFO] [am-log.com] Backend config specified via env: conf:phpfpm:tcp:172.16.238.10:9000 [INFO] [am-log.com] Backend PHP-FPM Remote: tcp://172.16.238.10:9000 vhost-gen: [INFO] Loading configuration file (-c): /etc/vhost-gen/mass-am-log.yml vhost-gen: [INFO] Loading vhost template (global) (-t): /et