ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
The goal is to change upstream definitions in nginx and be able to revert safely if the new configuration is not viable, without leaving stale backend references or interrupting in-flight requests. Reload via SIGHUP is documented to replace worker processes while preserving existing connections and applying new configuration. A syntax error in the new config
When using Traefik’s rate‑limit middleware (v2.9+), each instance maintains an independent leaky‑bucket counter set for the configured average and burst values. The documentation does not state whether these counters are cleared, kept, or partially retained when the dynamic configuration is reloaded (e.g., via file‑provider touch) or during a graceful shutdo
Envoy's hot restart mechanism permits configuration reload and binary swap via SIGHUP without dropping connections. A design question arises regarding how the admin API endpoint /runtime/health reports drain status when multiple Envoy peers initiate concurrent hot restarts while applying overlapping configuration changes. \n The documented capability indicat
After restoring an nginx configuration from a backup, the goal is to have the service start successfully and serve content using the restored files. The restored files must retain the original ownership (root:root) and permissions (644 for files, 755 for directories), and any SELinux contexts must match the original policy; otherwise the nginx worker process
nginx
traefikproxy