kjh2064
bd4bbdee57
ci / backend (push) Failing after 1s
ci / static (push) Failing after 7s
Build & Test with Secrets / build (push) Failing after 1s
ci / frontend (push) Failing after 1m29s
Build & Test with Secrets / frontend (push) Failing after 1m29s
ci / deploy (push) Has been skipped
Build & Test with Secrets / security-scan (push) Failing after 6s
Build & Test with Secrets / notification (push) Failing after 1s
deploy / deploy (push) Failing after 1m52s
deploy / notify (push) Successful in 1s
Modified .gitea/workflows/ci.yml: - Added 'deploy' job that runs on successful main push - Publishes Release build - Deploys to production server via SCP - Restarts systemd service - Performs health check Deployment flow: 1. Developer pushes to main 2. CI pipeline runs (static, backend, frontend tests) 3. If all tests pass → automatic deployment to production 4. Health check verifies deployment success Requirements: - DEPLOY_HOST: Production server hostname - DEPLOY_USER: SSH user - DEPLOY_KEY: SSH private key (set in Gitea Secrets) Status: Ready for production deployment Next: Set Gitea Actions Secrets and test Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>