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

[Feature] Periodical Backups as Config Parameter #10477

Open
2 of 7 tasks
DatDucati opened this issue Feb 26, 2020 · 4 comments
Open
2 of 7 tasks

[Feature] Periodical Backups as Config Parameter #10477

DatDucati opened this issue Feb 26, 2020 · 4 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented

Comments

@DatDucati
Copy link

  • Gitea version (or commit ref): not applicable
  • Git version: not applicable
  • Operating system: Ubuntu
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist: not relevant

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:

  • tighter control, whether a backup suceeded (Restore tests?)
  • (incremental backups Incremental backup of gitea #10135)
  • optional: file name schema
  • the absolute cherry on top would be configuration of an smb/rsync target
    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!
@stale
Copy link

stale bot commented Apr 26, 2020

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.

@stale stale bot added the issue/stale label Apr 26, 2020
@stale
Copy link

stale bot commented May 10, 2020

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed May 10, 2020
@zeripath zeripath reopened this May 10, 2020
@stale stale bot removed the issue/stale label May 10, 2020
@stale
Copy link

stale bot commented Jul 10, 2020

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.

@stale stale bot added the issue/stale label Jul 10, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Jul 11, 2020
@stale stale bot removed the issue/stale label Jul 11, 2020
@zyansheep
Copy link

zyansheep commented Aug 9, 2020

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 gitea dump.

EDIT: I wonder if SQL servers have an incremental backup feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented
Projects
None yet
Development

No branches or pull requests

4 participants