What problem does it solve? Official Sub2API Docker images sometimes lag behind a fork or main branch, forcing operators to build custom images and deploy them to production Compose stacks without breaking PostgreSQL, Redis, data, or rollback paths. This Skill provides a disciplined runbook for building an exact commit, deploying only the application image, and converging back to an official tagged release once it catches up. ## Core Features & Use Cases - Commit-Pinned Image Builds: Clone the fork into an isolated checkout, lock a full commit SHA, and build a linux/amd64 or linux/arm64 image with explicit VERSION, COMMIT, and DATE build arguments. - Safe Production Deployment: Back up PostgreSQL with pg_dump, pin a rollback image tag, patch only the application image line in the Compose file, and restart with --no-deps --pull never so databases are never recreated. - Official Image Convergence: Verify the official release commit is equal to or a descendant of the deployed fork commit using git merge-base before switching to a registry-backed official tag. - Cloudflare Tunnel Exposure: Run cloudflared as a container and diagnose public 502 errors caused by network-namespace or HTTP/HTTPS protocol mismatches. - Use Case: Your Sub2API server runs on a small ARM64 VPS and you need a fix that exists only in a fork commit. Use this Skill to build the image off-host, transfer it via docker save over SSH, deploy with a verified backup, and later converge back to the official weishaw/sub2api release tag. ## Quick Start Use the sub2api-fork-deploy skill to build commit abc123 from my Sub2API fork and deploy it to my Docker Compose server without touching PostgreSQL or Redis.