Skip to content

ci(deploy): use self-hosted production runner#136

Merged
fjbarrett merged 1 commit into
mainfrom
fix/prod-runner-deploy
Jul 22, 2026
Merged

ci(deploy): use self-hosted production runner#136
fjbarrett merged 1 commit into
mainfrom
fix/prod-runner-deploy

Conversation

@fjbarrett

Copy link
Copy Markdown
Owner

Summary

  • run the production cutover on the 24p-prod self-hosted runner instead of the stale pre-migration SSH endpoint
  • write deployment files directly to /opt/24p and use a temporary Docker credential directory
  • update the runner installer for Debian, pin v2.336.0, and verify the official release digest

Origin bootstrap

  • registered repository runner 24p-prod in Proxmox LXC 108
  • runner service is online under the dedicated deploy user
  • deploy belongs to the Docker group and owns /opt/24p
  • the Cloudflare tunnel remains the only public ingress; port 22 stays closed

Validation

  • actionlint (custom 24p-prod label acknowledged)
  • bash -n scripts/server/install-gh-runner.sh
  • shellcheck scripts/server/install-gh-runner.sh
  • docker compose config --quiet as deploy on the production origin
  • origin probes: / 200 and /api/health 200

OpenAI Codex assisted with the workflow migration, runner bootstrap, and validation. The commit includes a co-author trailer.

After the first successful main deployment, the obsolete PROD_DEPLOY_HOST and PROD_DEPLOY_SSH_KEY secrets can be removed.

Run the final deployment on the production container through an outbound GitHub runner.
This replaces the stale public SSH endpoint and keeps port 22 closed.

Update and verify the installer so the Debian origin can be bootstrapped reproducibly.

Co-Authored-By: OpenAI Codex <[email protected]>
@vercel

vercel Bot commented Jul 22, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
24p Ready Ready Preview, Comment Jul 22, 2026 3:09am

@fjbarrett
fjbarrett merged commit 0db3f01 into main Jul 22, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant