Harden fail2ban integration and mark task complete
This commit is contained in:
@@ -22,7 +22,7 @@ Reference: `Docs/Refactoring.md` for full analysis of each issue.
|
||||
- Introduce explicit factories or providers for shared resources such as DB, HTTP client session, scheduler, and settings.
|
||||
- Ensure routers depend on injected providers rather than global state or dynamic imports.
|
||||
|
||||
- **Harden fail2ban integration.**
|
||||
- **Harden fail2ban integration.** ✅
|
||||
- Remove the `sys.path` hack that locates `fail2ban-master` at runtime.
|
||||
- Replace it with a deterministic packaging or configuration model so the backend does not depend on repository layout.
|
||||
- Refactor `Fail2BanClient` so concurrency control is instance-based and not backed by hidden module globals.
|
||||
@@ -73,8 +73,8 @@ Reference: `Docs/Refactoring.md` for full analysis of each issue.
|
||||
### Priority Execution Plan
|
||||
|
||||
1. ✅ Fix the global SQLite connection pattern and tests.
|
||||
2. Refactor dependency injection / explicit shared resources.
|
||||
3. Harden fail2ban client concurrency and packaging.
|
||||
2. ✅ Refactor dependency injection / explicit shared resources.
|
||||
3. ✅ Harden fail2ban client concurrency and packaging.
|
||||
4. Convert setup guard to a safer startup-driven model.
|
||||
5. Add deployment-safe configuration and production-ready CORS.
|
||||
6. Add lifecycle and concurrency regression tests.
|
||||
|
||||
Reference in New Issue
Block a user