You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: Switch from GCR to GHCR for container registry
Switch Docker image publishing from Google Container Registry (GCR)
to GitHub Container Registry (GHCR) for better integration with
GitHub-native workflows.
Changes:
- Replace GCR workflow with GHCR workflow
- Use GITHUB_TOKEN instead of GCP service account
- Update all documentation references from GCR to GHCR
- Simplify authentication (no external secrets needed)
- Update README with GHCR pull commands
- Create comprehensive GHCR_SETUP.md guide
- Remove GCP_SETUP.md documentation
- Update docker-compose.yml with GHCR image option
Benefits of GHCR over GCR:
✅ No external setup required - works automatically
✅ Uses built-in GITHUB_TOKEN (no secrets to manage)
✅ Free for public images (unlimited storage/bandwidth)
✅ Native GitHub integration
✅ Automatic authentication in GitHub Actions
✅ Simpler configuration and troubleshooting
GitHub Actions Workflow:
- Publishes to ghcr.io/owner/repo/kb-processor-webapp
- Authenticates with GITHUB_TOKEN automatically
- Multi-architecture builds (amd64, arm64)
- Same tagging strategy (latest, stable, SHA, timestamp, branch)
- No repository secrets required
Image URLs:
- Latest: ghcr.io/owner/repo/kb-processor-webapp:latest
- By SHA: ghcr.io/owner/repo/kb-processor-webapp:a1b2c3d
- By branch: ghcr.io/owner/repo/kb-processor-webapp:branch-name
Documentation:
- GHCR_SETUP.md: Complete setup guide with authentication options
- README.md: Updated with GHCR commands and references
- docker-compose.yml: Shows both local build and GHCR image options
The workflow triggers automatically on pushes to main or claude/**
branches without any additional configuration.
0 commit comments