-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow prune to be on a different schedule #22
Comments
That's a good idea. My current plan is to have backup and prune as separate commands. That is so in swarm mode they can be separate services, orchestrated by something like swarm-cronjob. For standalone / docker-compose usage, we would just have a single |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This would be useful as I'd like to use the |
I am interested too on this. Can I help somehow @djmaze ? |
I can probably work on this in the next 7 days. As the swarm-cronjob approach is currently not feasible (at least for global jobs and we need a non-swarm solution as well, it probably makes sense to now separate into backup and prune containers with different schedules. I can have a stab at that. |
I would love it if prune could be on a different schedule. I have some backups that i run at a higher frequency like every 15 minutes at times but really only want prune to happen once a day. It would be ideal if i could set a different schedule for the prune or specify it to happen every X backups either option would work.
The text was updated successfully, but these errors were encountered: