kjh2064
43f58d57fd
Deploy to Production / Build Release (push) Failing after 36s
Deploy to Production / Pre-Deployment Verification (push) Has been skipped
Deploy to Production / Deploy to Production (push) Has been skipped
Deploy to Production / Health Check & Verification (push) Has been skipped
Deploy to Production / Deployment Report (push) Failing after 1s
【 Major Changes 】 - CLAUDE.md: CI/CD-Only Deployment Mandate • ALL production deployments MUST use Gitea Actions (manual SSH forbidden) • Reason: automatic validation, audit trail, consistent process, rollback safety 【 deploy-prod.yml: 5-Stage Enhanced Pipeline 】 - Stage 1: Build (restore, build, publish Release) - Stage 2: Pre-Check (SSH key + secrets validation) - Stage 3: Deploy (upload, extract, symlink, restart service) - Stage 4: Health Check (5-point verification: HTTP 200, login page, CSS, service status, commit hash) - Stage 5: Report (deployment summary + status) 【 SSH Key Management 】 - Support: DEPLOY_SSH_KEY_B64 (base64, recommended) OR DEPLOY_SSH_KEY (PEM, alternative) - Base64 encoding for safe secret transmission - Proper sed/chmod handling for Unix key format 【 Health Checks (Enhanced) 】 1. HTTP 200 on /Account/Login 2. Login page content verification 3. CSS file loads (/css/admin.css) 4. Service active status (systemctl) 5. Commit hash verification (deployed version matches) 【 Deployment Documentation 】 - Pre-deployment checklist - CI/CD deployment procedure (automatic + manual workflow_dispatch) - SSH key configuration guide (one-time setup) - Post-deployment monitoring - Troubleshooting guide - API monitoring (CLI commands) - Gitea Actions Workflows reference - Deployment Secrets configuration 【 Pattern Adopted from taxbaik 】 - deploy-prod.yml follows taxbaik v0.25.2 pattern (terse, production-proven) - SSH key base64 encoding - 5-point health checks instead of basic 3-retry - Comprehensive error handling + reporting Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>