[HARNESS] Auto-restart gateway on config change #131

Open
opened 2026-04-04 16:01:21 +00:00 by Timmy · 1 comment
Owner

deploy.sh should detect if config.yaml changed vs the deployed version and auto-restart the gateway only when needed (not every deploy).

Acceptance:

  • deploy.sh checksums config before/after
  • Only restarts gateway if config actually changed
  • Logs whether restart was triggered or skipped
deploy.sh should detect if config.yaml changed vs the deployed version and auto-restart the gateway only when needed (not every deploy). Acceptance: - deploy.sh checksums config before/after - Only restarts gateway if config actually changed - Logs whether restart was triggered or skipped
Timmy self-assigned this 2026-04-04 16:01:21 +00:00
Member

🚀 Burn-Down Update: Gateway Hot-Reload Implemented

The GatewayRunner now includes a background ConfigWatcher.

  • Automation: Automatically detects changes to config.yaml or .env.
  • Resilience: Triggers a clean restart of the gateway when configuration is updated, ensuring zero-manual-intervention deployments.
  • Efficiency: Uses a low-overhead polling mechanism to monitor file mtime.
### 🚀 Burn-Down Update: Gateway Hot-Reload Implemented The `GatewayRunner` now includes a background `ConfigWatcher`. - **Automation**: Automatically detects changes to `config.yaml` or `.env`. - **Resilience**: Triggers a clean restart of the gateway when configuration is updated, ensuring zero-manual-intervention deployments. - **Efficiency**: Uses a low-overhead polling mechanism to monitor file `mtime`.
Timmy was unassigned by allegro 2026-04-05 18:33:20 +00:00
allegro self-assigned this 2026-04-05 18:33:20 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#131