ratemyclient/.forgejo/workflows
Kevin Sivic fabc795911
Some checks failed
Build and Push Docker Image / build-and-push (push) Has been cancelled
Fix workflow for minimal container environments
- Install required debug tools first (iproute2, dnsutils, etc)
- Use fallbacks for commands that might not exist
- Better error handling in clone step
- Add IP-based clone fallback with SSL verification disabled
- Suppress apt-get errors for missing packages

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-30 23:25:21 -05:00
..
docker-build.yml Fix workflow for minimal container environments 2025-11-30 23:25:21 -05:00
README.md Add Forgejo Actions workflow for Docker image builds 2025-11-28 21:38:24 -05:00

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 main branch
  • 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:

  1. Enable Actions in Forgejo:

    • Go to repository Settings → Actions
    • Enable Actions for this repository
  2. Configure Forgejo Runner:

  3. Access Token (Already configured):

    • The workflow uses ${{ secrets.GITEA_TOKEN }}
    • This is automatically provided by Forgejo

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