Skip to content
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

Closed
seertenedos opened this issue Dec 22, 2019 · 5 comments · Fixed by #36
Closed

Allow prune to be on a different schedule #22

seertenedos opened this issue Dec 22, 2019 · 5 comments · Fixed by #36

Comments

@seertenedos
Copy link

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.

@djmaze
Copy link
Owner

djmaze commented Jan 31, 2020

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 CRON variable which just runs the command given to the current container (either backup or prune).

@stale
Copy link

stale bot commented Mar 31, 2020

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.

@stale stale bot added the wontfix label Mar 31, 2020
@stale stale bot closed this as completed Apr 7, 2020
@djmaze djmaze reopened this Apr 8, 2020
@stale stale bot removed the wontfix label Apr 8, 2020
@azurefreecovid
Copy link

azurefreecovid commented May 27, 2020

This would be useful as I'd like to use the restic check on a schedule as well

@zoispag
Copy link

zoispag commented May 27, 2020

I am interested too on this. Can I help somehow @djmaze ?

@djmaze
Copy link
Owner

djmaze commented May 27, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants