As requested in Discussion #4379 , here is the same suggestion as a feature request
I’m running the container on a Synology NAS, and overall it works great.
The only issue I’m having is with updates. Synology doesn’t update the container automatically, so updates have to be done manually or through a tool like Watchtower, which is what I’m currently using.
I have Watchtower scheduled to run at 2:00 AM. It checks for updates, updates the container if needed, and restarts it. The problem is that this can interfere with the website checks that are scheduled to run around the same time.
It would be great to have an option to define a maintenance window during which all scans are temporarily delayed. Once the maintenance window has passed and the container is back up, the scans could automatically resume.
This would help avoid timeout errors caused by scheduled container restarts between ChangeDetection, sockpuppetbrowser and other containers cause by high CPU load.
Thanks
As requested in Discussion #4379 , here is the same suggestion as a feature request
I’m running the container on a Synology NAS, and overall it works great.
The only issue I’m having is with updates. Synology doesn’t update the container automatically, so updates have to be done manually or through a tool like Watchtower, which is what I’m currently using.
I have Watchtower scheduled to run at 2:00 AM. It checks for updates, updates the container if needed, and restarts it. The problem is that this can interfere with the website checks that are scheduled to run around the same time.
It would be great to have an option to define a maintenance window during which all scans are temporarily delayed. Once the maintenance window has passed and the container is back up, the scans could automatically resume.
This would help avoid timeout errors caused by scheduled container restarts between ChangeDetection, sockpuppetbrowser and other containers cause by high CPU load.
Thanks