feat: add internal WordPress cron runner

2026-07-23 23:40:44 +02:00
parent f75bce3dea
commit e6ec3c94dc
15 changed files with 245 additions and 24 deletions
@@ -11,6 +11,8 @@ docker compose --profile tools run --rm wp-cli /scripts/bootstrap.sh

 NGINX binds to loopback ports 8080/8443. WordPress and MariaDB remain private. The
 bootstrap is safe to rerun and does not duplicate demo records.
+The internal `wp-cron` service runs scheduled WordPress events after the bootstrap
+completes.

 The default persistent paths are host-based bind mounts under `./runtime`. Before the
 first start, run:
@@ -37,6 +39,9 @@ Required controls:
 - either direct Let's Encrypt termination or a trusted external load balancer;
 - off-host database/file backups and monitoring.

+The default `wp-cron` service handles scheduled WordPress events internally and should
+remain enabled unless another controlled cron runner replaces it.
+
 When a load balancer terminates TLS, Certbot stays disabled. `TRUST_PROXY_HEADERS=1`
 is safe only when firewall/network policy makes the load balancer the sole NGINX
 caller and it overwrites `X-Forwarded-*` headers.