-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
[Feature] Periodical Backups as Config Parameter #10477
Comments
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. You can re-open it if needed. |
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
This would be pretty nice to have and it seems pretty easy to implement. Store the last backup time and see if a certain amount of time has passed. If it has, depending on config, either replace the last backup or create a new file with EDIT: I wonder if SQL servers have an incremental backup feature. |
[x]
):Description
I already know about the gitea dump command. But sadly automating it is rather cumbersome and if it was an configurable entity of gitea, it would make the management of backups much better. It would provide various benefits such as:
I would like to help, but I haven't looked much into it. If I get some pointers where one should start, feel free to do so!
The text was updated successfully, but these errors were encountered: