7 commits

Author	SHA1	Message	Date
James Paterni	c85c4a897b	Improve Forgejo Actions workflow documentation and error handling ... - Add better secret configuration documentation with required status - Include clear setup instructions for DOCKER_IMAGE_NAME secret - Add validation check for missing DOCKER_IMAGE_NAME secret - Improve troubleshooting section with Docker push errors - Add helpful error messages for configuration issues 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-15 17:22:21 -04:00
James Paterni	2217d552c1	Simplify Forgejo Actions and fix container state test ... Workflow Simplification: - Consolidate 8 workflows into 1 comprehensive ci.yml workflow - Delete redundant workflows: test.yml, build.yml, docker.yml, minimal.yml, node-ruby.yml, shell-only.yml, simple.yml - Keep shell-based approach for maximum Forgejo runner compatibility - Update README.md to document simplified single-workflow design Test Fix: - Fix failing container_spec.rb test for missing state information - Add missing json method mock to handle fallback scenario - All 121 tests now passing The single workflow provides: - Test job: Install dependencies and run RSpec tests - Build job: Build Docker image and push to Docker Hub - Notify job: Report pipeline status - Full compatibility with any Forgejo runner configuration 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-15 11:48:37 -04:00
James Paterni	6e7adc330f	Fix working directory errors in Forgejo Actions workflows ... - Remove working-directory defaults that caused chdir errors - Use explicit 'cd app' commands in all Ruby-related steps - Fix ci.yml, test.yml, docker.yml, and shell-only.yml workflows - Update documentation with working directory troubleshooting The error occurred because working-directory was set before repository checkout, causing the container to try to start in a non-existent directory. Resolves: "chdir to cwd (..../app) set in config.json failed: no such file" 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-15 11:40:10 -04:00
James Paterni	20ee57f0c2	Fix package manager detection and add shell-only workflow ... - Add robust package manager auto-detection (apk, apt-get, yum, dnf) - Support for Alpine, Debian/Ubuntu, CentOS/RHEL, Fedora - Create shell-only.yml workflow with no GitHub Actions dependencies - Update all workflows to handle different runner environments - Comprehensive error handling and fallback mechanisms - Updated documentation with new troubleshooting guidance Resolves: - "apk: command not found" errors - "node: executable file not found" errors - Compatibility with various Forgejo runner configurations 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-15 11:29:20 -04:00
James Paterni	e294b9b1a3	Fix Node.js executable error in Forgejo Actions workflows ... - Install Node.js before checkout in all workflows that use actions - Updated ci.yml, test.yml, build.yml, and docker.yml - Updated README.md with fix information - Resolves "exec: node: executable file not found in $PATH" error 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-15 11:25:02 -04:00
James Paterni	95ba7f39c1	Fix Node.js executable error in Forgejo Actions ... ## Problem Forgejo Actions failed with error: ``` OCI runtime exec failed: exec failed: unable to start container process: exec: "node": executable file not found in $PATH: unknown ``` ## Root Cause GitHub Actions like checkout@v4, cache@v4, and upload-artifact@v4 require Node.js runtime, but Ruby Alpine containers don't include Node.js by default. ## Solutions Implemented ### 1. Updated Existing Workflows - **ci.yml**: Added Node.js installation (`apk add nodejs npm`) - **test.yml**: Added Node.js installation for GitHub Actions compatibility ### 2. New Alternative Workflows - **node-ruby.yml**: Uses Node.js 18 Alpine base with Ruby installed - **simple.yml**: Shell-based workflow avoiding Node.js actions - **minimal.yml**: Minimal test-only workflow with basic shell commands ### 3. Updated Documentation - Added troubleshooting section for Node.js issues - Documented all workflow options with their trade-offs - Provided clear solutions for different use cases ## Workflow Options ### For Full GitHub Actions Support - Use `node-ruby.yml` (Node.js base + Ruby) - Use `ci.yml` or `test.yml` (Ruby base + Node.js installed) ### For Minimal Dependencies - Use `simple.yml` (shell-based, manual git/docker) - Use `minimal.yml` (basic test execution only) ### For Production - Use `node-ruby.yml` for maximum compatibility - Use `simple.yml` for minimal resource usage ## Benefits - **Multiple Options**: Choose workflow based on needs - **Backward Compatibility**: Existing workflows still work - **Minimal Alternatives**: Avoid Node.js dependency if not needed - **Clear Documentation**: Troubleshooting guide for common issues This provides flexibility to use Forgejo Actions with or without Node.js dependencies based on specific requirements. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-15 11:18:12 -04:00
James Paterni	5dcdc28356	Add Forgejo Actions workflows for CI/CD ... ## Forgejo Actions Setup ### Directory Structure - `.forgejo/workflows/` - Forgejo Actions workflows directory - `ci.yml` - Main CI pipeline (test + build + notify) - `test.yml` - Test-only workflow for development - `build.yml` - Build-only workflow for releases - `docker.yml` - Advanced Docker workflow with caching - `README.md` - Comprehensive documentation ### Key Features #### 1. Main CI Pipeline (ci.yml) - Runs RSpec tests in Ruby 3.3 Alpine container - Builds and pushes Docker images to Docker Hub - Supports version tagging and latest tags - Provides pipeline status notifications #### 2. Test Workflow (test.yml) - Dedicated testing workflow for PRs - Runs unit and integration tests separately - Generates coverage reports - Uploads test artifacts #### 3. Build Workflow (build.yml) - Standalone Docker build workflow - Triggers on main branch and version tags - Includes build status notifications #### 4. Advanced Docker Workflow (docker.yml) - Uses Docker Buildx for advanced builds - Implements Docker layer caching - Automatic metadata extraction and tagging ### Forgejo vs GitHub Actions Differences #### Technical Adaptations - **Directory**: `.forgejo/workflows/` vs `.github/workflows/` - **Runners**: `runs-on: docker` with container specification - **Dependencies**: Explicit Alpine package installation - **Caching**: Adapted for Forgejo environment - **Execution**: Optimized for Docker container runtime #### Compatibility - Uses same action references (`actions/checkout@v4`, etc.) - Same secret management (`${{ secrets.* }}`) - Same environment variables (`${{ github.* }}`) - Maintains workflow syntax compatibility ### Required Configuration - Enable Repository Actions in Forgejo settings - Configure Docker Hub secrets (DOCKER_USERNAME, DOCKER_PASSWORD, DOCKER_IMAGE_NAME) - Ensure Forgejo Runner is installed and configured - Set up action repository sources ### Benefits - **Dual CI/CD**: Can run alongside GitHub Actions - **Self-hosted**: Full control over CI/CD infrastructure - **Docker-native**: Optimized for containerized workflows - **Feature parity**: Maintains same functionality as GitHub Actions This enables Baktainer to run on Forgejo instances with full CI/CD capabilities while maintaining compatibility with existing GitHub Actions. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-07-15 11:02:58 -04:00