What problem does it solve? Upgrading a self-hosted backend behind a running Pingora gateway risks downtime if the gateway is restarted or traffic is switched prematurely. This Skill provides a strict blue/green rollout procedure that keeps the gateway on port 39180 alive while a new backend binary is built, verified, and cut over via config edit plus SIGHUP. ## Core Features & Use Cases - Blue/Green Slot Rollout: Runs the candidate backend on the inactive slot (39080 or 39081) while the active slot keeps serving traffic. - In-Process Gateway Reload: Applies the active_upstream config change with kill -HUP <gateway-pid> only, never restarting the gateway process. - Stable-Path Verification and Rollback: Requires repeated health checks through 39180 and the public domain before declaring success, with config-restore rollback if checks fail. - Use Case: You deploy a new StaticFlow backend build in a tmux-supervised production setup. The Skill walks you through preflight topology checks, capped-parallelism build, candidate startup, cutover, verification, and safe cleanup of the old slot. ## Quick Start Use this skill to roll out the newly built StaticFlow backend to the inactive slot and switch gateway traffic without restarting the gateway.
