history archive router precedence + endpoint/source tests + history sync register test + task status update
This commit is contained in:
@@ -9,6 +9,7 @@ Reference: `Docs/Refactoring.md` for full analysis of each issue.
|
||||
## Open Issues
|
||||
|
||||
1. Ban history durability and fail2ban DB size management
|
||||
- status: completed
|
||||
- description: BanGUI currently reads fail2ban history directly, but fail2ban's `dbpurgeage` may erase old history and can cause DB growth issues with long retention. Implement a BanGUI-native persistent archive and keep fail2ban DB short-lived.
|
||||
- acceptance criteria:
|
||||
- BanGUI can configure and fetch fail2ban `dbpurgeage` and `dbfile` from server API.
|
||||
|
||||
Reference in New Issue
Block a user