739895d81e
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
docs/issues - Issue Specification Files
This directory contains markdown files that are automatically converted to GitHub Issues when merged to main or development.
How It Works
- Create a markdown file in this directory using the template format
- Add YAML frontmatter with issue metadata (title, labels, priority, etc.)
- Merge to main/development - the
docs-to-issues.ymlworkflow runs - GitHub Issue is created with your specified metadata
- File is moved to
docs/issues/created/to prevent duplicates
Quick Start
Copy _TEMPLATE.md and fill in your issue details:
---
title: "My New Issue"
labels:
- feature
- backend
priority: medium
---
# My New Issue
Description of the issue...
Frontmatter Fields
| Field | Required | Description |
|---|---|---|
title |
Yes* | Issue title (*or uses first H1 as fallback) |
labels |
No | Array of labels to apply |
priority |
No | critical, high, medium, low |
milestone |
No | Milestone name |
assignees |
No | Array of GitHub usernames |
parent_issue |
No | Parent issue number for linking |
create_sub_issues |
No | If true, each ## Section becomes a sub-issue |
Sub-Issues
To create multiple related issues from one file, set create_sub_issues: true:
---
title: "Main Testing Issue"
labels: [testing]
create_sub_issues: true
---
# Main Testing Issue
Overview content for the parent issue.
## Unit Testing
This section becomes a separate issue.
## Integration Testing
This section becomes another separate issue.
Manual Trigger
You can manually run the workflow with:
# Dry run (no issues created)
gh workflow run docs-to-issues.yml -f dry_run=true
# Process specific file
gh workflow run docs-to-issues.yml -f file_path=docs/issues/my-issue.md
Labels
Labels are automatically created if they don't exist. Common labels:
- Priority:
critical,high,medium,low - Type:
feature,bug,enhancement,testing,documentation - Component:
backend,frontend,ui,security,caddy,database