|
|
|
@ -54,8 +54,8 @@ we choose this loosely coupled method. Events which are yet unprocessed are bein
|
|
|
|
|
Events are processed from the moment the initial backup is configured, when disabling backups, the (local) changelog itself
|
|
|
|
|
remains active.
|
|
|
|
|
|
|
|
|
|
On periodic intervals (the standard ones from the backup scheduler), the collected commits are pushed to the configured
|
|
|
|
|
upstream repository. To shorten these default intervals, a custom cronjob (see :doc:`Settings </manual/settingsmenu>`) can be
|
|
|
|
|
Git backup will push collected commits to the upstream repository nightly.
|
|
|
|
|
To shorten this default interval, a custom cronjob (see :doc:`Settings </manual/settingsmenu#cron>`) 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.
|
|
|
|
|
|
|
|
|
|