I’m using the saspus/duplicacy-web docker on unRAID. The setup was super smooth and had my first backup to B2 in less than 30 minutes. Thank you!
However, after running a single backup, I noticed the duplicacy_web logs quickly ballooned. It appears to log every page access which seems excessive; especially when there’s a new log every second while backups are running.
2023/01/10 11:42:13 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:14 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:15 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:16 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:17 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:18 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:19 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:20 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:21 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:22 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:23 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:24 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:25 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:26 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:27 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:28 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:29 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
2023/01/10 11:42:30 xxx.xxx.xxx.xxx:56646 POST /get_backup_status
These logs aren’t very useful [to me]. They bloat the logs and get in the way of any sort of debugging I may need to do. Is it possible to disable these kinds of access logs?