6 Commits

Author	SHA1	Message	Date
GitHub Actions	739895d81e	fix(security): resolve CrowdSec startup and permission issues ... Fixes CrowdSec not starting automatically on container boot and LAPI binding failures due to permission issues. Changes: - Fix Dockerfile: Add charon:charon ownership for CrowdSec directories - Move reconciliation from routes.go goroutine to main.go initialization - Add mutex protection to prevent concurrent reconciliation - Increase LAPI startup timeout from 30s to 60s - Add config validation in entrypoint script Testing: - Backend coverage: 85.4% (✅ meets requirement) - Frontend coverage: 87.01% (✅ exceeds requirement) - Security: 0 Critical/High vulnerabilities (✅ Trivy + Go scans) - All CrowdSec-specific tests passing (✅ 100%) Technical Details: - Reconciliation now runs synchronously during app initialization (after DB migrations, before HTTP server starts) - Maintains "GUI-controlled" design philosophy per entrypoint docs - Follows principle of least privilege (charon user, not root) - No breaking changes to API or behavior Documentation: - Implementation guide: docs/implementation/crowdsec_startup_fix_COMPLETE.md - Migration guide: docs/implementation/crowdsec_startup_fix_MIGRATION.md - QA report: docs/reports/qa_report_crowdsec_startup_fix.md Related: #crowdsec-startup-timeout	2025-12-23 01:59:21 +00:00
GitHub Actions	af8384046c	chore: implement instruction compliance remediation ... - Replace Go interface{} with any (Go 1.18+ standard) - Add database indexes to frequently queried model fields - Add JSDoc documentation to frontend API client methods - Remove deprecated docker-compose version keys - Add concurrency groups to all 25 GitHub Actions workflows - Add YAML front matter and fix H1→H2 headings in docs Coverage: Backend 85.5%, Frontend 87.73% Security: No vulnerabilities detected Refs: docs/plans/instruction_compliance_spec.md	2025-12-21 04:08:42 +00:00
GitHub Actions	2a6175a97e	feat: Implement CrowdSec toggle fix validation and documentation updates ... - Added QA summary report for CrowdSec toggle fix validation, detailing test results, code quality audit, and recommendations for deployment. - Updated existing QA report to reflect the new toggle fix validation status and testing cycle. - Enhanced security documentation to explain the persistence of CrowdSec across container restarts and troubleshooting steps for common issues. - Expanded troubleshooting guide to address scenarios where CrowdSec does not start after a container restart, including diagnosis and solutions.	2025-12-15 07:30:36 +00:00
GitHub Actions	51f0a6937e	feat: Implement database migration command and enhance CrowdSec startup verification ... - Added TestMigrateCommand_Succeeds to validate migration functionality. - Introduced TestStartupVerification_MissingTables to ensure proper handling of missing security tables. - Updated crowdsec_startup.go to log warnings for missing SecurityConfig table. - Enhanced documentation for database migrations during upgrades, including steps and expected outputs. - Created a detailed migration QA report outlining testing results and recommendations. - Added troubleshooting guidance for CrowdSec not starting after upgrades due to missing tables. - Established a new plan for addressing CrowdSec reconciliation failures, including root cause analysis and proposed fixes.	2025-12-15 07:30:36 +00:00
GitHub Actions	aa55d38a82	fix: enhance CrowdSec startup logic and verification, improve error handling in Security page	2025-12-15 07:30:36 +00:00
GitHub Actions	e41c4a12da	fix: resolve CrowdSec 500 error and state mismatch after container restart ... - Make Stop() idempotent: return nil instead of error when PID file missing - Add startup reconciliation: auto-start CrowdSec if DB says enabled - Ensure log file exists for LogWatcher to prevent disconnection Fixes: - "Failed to stop CrowdSec: 500 error" when toggling off - CrowdSec showing "not running" despite being enabled in settings - Live logs showing disconnected after container restart	2025-12-15 07:30:35 +00:00