Summary
Create a dedicated LXC container as a shared GitHub Actions self-hosted runner for all repos (mcp2cli, king-ng, future projects).
Current State
- king-ng has a repo-level runner (
king-ng-lxc) -- tied to that repo only
- mcp2cli has no runner -- Claude Code Review workflow needs one to reach LiteLLM
Proposed Setup
- New LXC on Proxmox dedicated to CI
- Install: Bun, Node.js, GitHub Actions runner agent
- Register as repo-level runner for each project (personal accounts can't use org runners)
- Labels:
self-hosted, ci, plus project-specific labels as needed
- Network access to LiteLLM (10.71.20.53:4000) for Claude review workflows
- Secret
LITELLM_API_KEY set on each repo that uses Claude review
Migration
- Move king-ng's runner from
king-ng-lxc to the shared CI LXC
- Update workflow labels from
king-ng to ci (or keep both as labels)
Depends On
/deploy-service skill for LXC provisioning
Summary
Create a dedicated LXC container as a shared GitHub Actions self-hosted runner for all repos (mcp2cli, king-ng, future projects).
Current State
king-ng-lxc) -- tied to that repo onlyProposed Setup
self-hosted,ci, plus project-specific labels as neededLITELLM_API_KEYset on each repo that uses Claude reviewMigration
king-ng-lxcto the shared CI LXCking-ngtoci(or keep both as labels)Depends On
/deploy-serviceskill for LXC provisioning