deploy-hosted-gateway

Deploys the hosted Gateway container to Azure via a GitHub Actions workflow and verifies health.

96|11|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/thefrederiksen/devthrottle --skill deploy-hosted-gateway-thefrederiksen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-hosted-gateway
Source: https://github.com/thefrederiksen/devthrottle/tree/main/.claude/skills/deploy-hosted-gateway
Command: npx skills add https://github.com/thefrederiksen/devthrottle --skill deploy-hosted-gateway-thefrederiksen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Updating the live cloud Gateway (which also ships the Cockpit and mobile app in one container image) requires a controlled, measured process. This Skill provides the single authorized path to redeploy the hosted service on Azure, preventing unmeasured outages caused by manual changes through the Azure Portal or ad-hoc az commands. ## Core Features & Use Cases - Guided production deploy: Starts the deploy-hosted-gateway.yml GitHub Actions workflow against main, watches the run to completion, and confirms the live service returns HTTP 200 on /healthz. - Outage measurement and reporting: Explains the expected ~60 second in-place restart outage on the Basic B2 plan, enforces the 120-second budget, and reports the measured number to the human. - Rollback path: Describes how to restore a previous image (including last-known-good) via the rollback-hosted-gateway.yml workflow when a deploy ships bad code. - Use Case: After merging a fix to main, ask the agent to deploy the hosted Gateway; it confirms your explicit go-ahead, triggers the workflow, monitors the run, verifies health, and reports the measured outage. ## Quick Start Ask the agent to deploy the hosted Gateway to production and confirm the live service is healthy afterwards.

Frequently Asked Questions about deploy-hosted-gateway

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

FAQPage Schema
How do I deploy the hosted Gateway to production?▼

Run gh workflow run deploy-hosted-gateway.yml --repo thefrederiksen/devthrottle --ref main after getting explicit human approval. Then watch the run with gh run watch and confirm https://devthrottle-gw.azurewebsites.net/healthz returns HTTP 200.

How do I deploy the Cockpit or mobile app?▼

Use this same Gateway deploy. The Cockpit and mobile app are built into the Gateway container image at wwwroot/c and wwwroot/mobile, so there is no separate Cockpit or mobile deployment workflow.

Does the deploy wait for CI checks to pass?▼

No. The workflow refuses only checks that have completed and failed, and it refuses any ref other than main. Pending checks are listed but do not block the deploy, and a commit with no checks is not refused.

How much downtime does a Gateway deploy cause?▼

Expect about 60 seconds of outage because the Basic B2 plan has no deployment slots, so the deploy is an in-place container restart. The run fails if the measured outage exceeds the 120-second budget.

How do I roll back a bad Gateway deploy?▼

Run gh workflow run rollback-hosted-gateway.yml with -f commit=last-known-good or a short commit hash. This pins a previous image and restarts, which takes a minute or two but does not undo database changes shipped with the bad deploy.

Why does the deploy fail at Azure login (OIDC)?▼

The Azure federated credential trust is missing or misconfigured. The app registration must carry a federated credential with subject repo:thefrederiksen/devthrottle:environment:hosted-gateway-production, which requires Azure tenant access to fix.