skills.rest
acking-you
acking-youCOMMUNITY
Explore all skills by this author →
GitHub

selfhosted-gateway-seamless-upgrade

Coordinate zero-downtime StaticFlow gateway upgrades behind Pingora with blue/green slots and SIGHUP cutover.

Updated Aug 23, 2026
Search Tags:#tmux#uptime#zero-downtime#blue-green#gateway#cutover#sighup
One-click install
npx skills add https://github.com/acking-you/static_flow --skill selfhosted-gateway-seamless-upgrade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: selfhosted-gateway-seamless-upgrade
Source: https://github.com/acking-you/static_flow/tree/main/skills/selfhosted-gateway-seamless-upgrade
Command: npx skills add https://github.com/acking-you/static_flow --skill selfhosted-gateway-seamless-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade the local StaticFlow backend behind the Pingora gateway without downtime in a tmux-supervised production setup, using blue/green backend slots and SIGHUP-driven cutovers.

Core Features & Use Cases

  • Non-disruptive rollout: perform upgrades without stopping the gateway.
  • Blue/green slot management: select the inactive slot, verify readiness, and perform the cutover with SIGHUP.
  • Guardrails and rollback: preflight checks, health verification, and rollback procedures in case of failure.

Quick Start

Initiate a blue/green upgrade by selecting the inactive slot, build and start the candidate backend, update the gateway's active_upstream with the candidate, and verify stable-path health before finalizing the cutover.

Frequently Asked Questions about selfhosted-gateway-seamless-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade a gateway without downtime in a tmux production environment?▼

Blue/green slot management selects the inactive backend slot, builds and starts the candidate, updates the gateway's active_upstream, and verifies stable-path health before finalizing the SIGHUP cutover. Rollback procedures are triggered if stability verification fails.

Can I use SIGHUP to reload a Pingora gateway configuration without dropping connections?▼

Preflight checks verify the inactive blue/green slot, build the candidate backend, start it, and confirm stable-path health before updating the gateway's active_upstream. This guarantees the new backend is ready before any SIGHUP cutover occurs.

What happens if a gateway upgrade fails during a blue/green cutover?▼

Failed gateway upgrades trigger rollback procedures that revert the active_upstream to the previous stable blue/green slot. Health verification runs after cutover to detect failures and automatically guard against disrupted updates.

Does this zero-downtime upgrade approach require a specific gateway port or backend setup?▼

This zero-downtime upgrade requires a tmux-supervised production environment with a running gateway on port 39180 and pre-configured blue/green backend slots. The active slot must remain undisrupted during the rollout process.

Related Skills

Explore More Software Engineering Skills→
UnicornUnicorn

deploy-agent

Designs blue-green, canary and rolling deployment strategies for web services and APIs with rollback procedures, health checks, and monitoring integration.

Official
Intermediate
anthony-chaudharyanthony-chaudhary
30

stability-score

Audit git-tracked repositories against stability KPIs and generate a JSON scorecard report.

Community
Advanced
ryukyagamilightryukyagamilight
1

load-balancer

Configure HAProxy and Nginx for HTTP and TCP load balancing.

Community
Intermediate
heaptracetechnologyheaptracetechnology
13

Deploy to ECS

Automate ECS deployments with Fargate or EC2 launch types.

Community
Advanced