Skip to content

git-backup: hint to cronjobs for shorter backup intervals #315

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.

Sign up for GitHub

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

Merged
AdSchellevis merged 1 commit into from
Feb 25, 2021
Merged

git-backup: hint to cronjobs for shorter backup intervals #315

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions source/manual/git-backup.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,8 +55,9 @@ we choose this loosely coupled method. Events which are yet unprocessed are bein
remains active.

On periodic intervals (the standard ones from the backup scheduler), the collected commits are pushed to the configured
upstream repository. The regular backup procedure (which is also being triggered using the test button in the user interface)
is responsible for initialising the empty local repository and configuring the upstream target.
upstream repository. To shorten these default intervals, a custom cronjob (see :doc:`Settings </manual/settingsmenu>`) can be
set up, selecting `Remote Backup` as the Command. The regular backup procedure (which is also being triggered using the test
button in the user interface) is responsible for initialising the empty local repository and configuring the upstream target.

.. Note::

Expand Down