|
All checks were successful
Build and Push Docker Image / build-and-push (push) Successful in 15s
Change from GITEA_TOKEN to FORGEJO_TOKEN to match the configured repository secret. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| docker-build.yml | ||
| README.md | ||
Forgejo Actions Workflows
This directory contains CI/CD workflows for the RateMyClient project.
docker-build.yml
Automatically builds and pushes Docker images to the Forgejo Container Registry.
What it does:
- Triggers on push to
mainbranch - Builds the Docker image using the Dockerfile
- Pushes to
forgejo.sivic.me/kevinsivic/ratemyclient - Tags images with:
latest(for main branch)- Branch name
- Git commit SHA
- Semantic versions (if tagged)
Setup Required:
-
Enable Actions in Forgejo:
- Go to repository Settings → Actions
- Enable Actions for this repository
-
Configure Forgejo Runner:
- Forgejo needs a runner to execute workflows
- Follow: https://forgejo.org/docs/latest/admin/actions/
-
Access Token (Already configured):
- The workflow uses
${{ secrets.GITEA_TOKEN }} - This is automatically provided by Forgejo
- The workflow uses
Image Location:
After successful build, pull the image:
docker pull forgejo.sivic.me/kevinsivic/ratemyclient:latest
Deploy with the built image:
Update your docker-compose.yml to use the registry image:
services:
web:
image: forgejo.sivic.me/kevinsivic/ratemyclient:latest
# Remove 'build: .' line
Manual Trigger:
You can also trigger builds manually from: Repository → Actions → Build and Push Docker Image → Run workflow