Commit graph

2 commits

Author SHA1 Message Date
85941b5960 Fix Dockerfile for Alpine, update deployment to use custom image
All checks were successful
Test CI / test (pull_request) Successful in 0s
- Base image is Alpine Linux, not Debian - use apk instead of apt-get
- Switch to root for package install, then back to user 1000
- Add musl-dev for C compilation, docker-cli for container builds
- Update deployment to use registry.tail8d86e.ts.net/blumeops/forgejo-runner:latest

Image built and pushed to zot registry.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-23 18:42:24 -08:00
15976f90d6 Reorganize CI/CD bootstrap phases, add custom runner Dockerfile
All checks were successful
Test CI / test (pull_request) Successful in 0s
- Reorder phases: P2 is now Custom Runner Image (was Mirror & Build)
- Add P3 for Mirror Forgejo & Build from Source
- Rename P3 -> P4 (Self-Deploy), P4 -> P5 (Container Builds)
- Update overview with new phase structure and host mode notes
- Add Dockerfile for custom runner with Node.js, npm, docker, build tools
- Address chicken-and-egg problem: bootstrap manually, then automate
- Document cross-compilation challenge for macOS ARM64 target

Key insight: Stock runner lacks Node.js, so actions/checkout@v4 doesn't
work. Building custom runner image is prerequisite for everything else.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-23 18:18:23 -08:00