3 Commits

Author	SHA1	Message	Date
SysAdmin	8a70e4aad1	fix: Replace GitHub Actions with native git commands for Gitea compatibility ... Issues Fixed: 1. Gitea Actions runner lacks Node.js (required for actions/checkout@v4) 2. Gitea Actions doesn't support actions/upload-artifact@v4 3. Build jobs were unnecessary overhead Solution: - Replaced actions/checkout@v4 with native git clone commands - Removed separate build jobs (build-littleshop, build-telebot) - Build Docker images directly on deployment targets via SSH - Simplified workflow: deploy jobs now handle clone + build + deploy Benefits: - No Node.js dependency - uses native git/docker only - Faster deployments - no image transfer overhead - Simpler pipeline - fewer jobs and steps - Better resource usage - builds on target server with proper resources Changes: - deploy-production: Builds images on VPS from git checkout - deploy-preproduction: Builds images on CT109 from git checkout - Removed artifact upload/download steps entirely - Git clone/checkout happens on deployment targets 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-11-16 21:08:01 +00:00
SysAdmin	b04de045c5	fix: Remove Docker buildx setup to resolve CI/CD permissions error ... Issue: - Docker buildx creates containerized builder requiring elevated capabilities - Gitea Actions runner doesn't have permission to apply Linux capabilities - Error: "unable to apply caps: operation not permitted" Solution: - Removed docker/setup-buildx-action from both build jobs - Using standard docker build (already configured via DOCKER_BUILDKIT=1) - BuildKit features still enabled via environment variable Impact: - CI/CD builds will now succeed without capability errors - No functionality lost (workflow uses 'docker build', not 'docker buildx build') - Faster build start (no buildx container creation overhead) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-11-16 21:05:09 +00:00
SysAdmin	47e43d4ff8	ci: Migrate from GitLab CI/CD to Gitea Actions with CT109 pre-production ... **Migration Complete:** - Removed GitLab CI/CD configuration (.gitlab-ci.yml) - Created Gitea Actions workflows (.gitea/workflows/) - Disabled automatic production deployment (manual only) - Added pre-production deployment to CT109 Docker container **New Workflows:** - build-and-deploy.yml: Main CI/CD pipeline with CT109 deployment - rollback.yml: Manual rollback capability - README.md: Comprehensive workflow documentation **Pre-Production Environment (CT109):** - Host: 10.0.0.51 - User: sysadmin - Port: 22 - Deploys on push to development/main branches - Access URL: http://ct109.local:5100 **Documentation:** - CI_CD_MIGRATION_GITEA.md: Complete migration guide - CI_CD_CT109_PREPRODUCTION.md: CT109 deployment architecture - GITEA_SECRETS_SETUP_GUIDE.md: Secrets configuration instructions **Git Remote Updated:** - Migrated from GitLab (gitlab.silverlabs.uk) to Gitea (git.silverlabs.uk) - Using token authentication for push/pull operations **Next Steps:** 1. Push code to Gitea to create repository 2. Add CT109 secrets via Gitea UI (CT109_HOST, CT109_SSH_PORT, CT109_USER, CT109_SSH_KEY) 3. Test pre-production deployment workflow 🚀 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>	2025-11-14 19:10:14 +00:00