| commit | fbe3b345424c021df76d0982eef1786ba815829d | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Thu Feb 20 16:55:01 2025 +0000 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Thu Feb 20 16:55:01 2025 +0000 |
| tree | b286dbd8fdb86aadb218d7bf903a7d2f1771c285 | |
| parent | b9cba775af0e2a8d9ba3d3419044f81190475022 [diff] | |
| parent | 2dacb24719a6006f1929eb338dcd9d80c068d1f0 [diff] |
Merge branch 'stable-3.11' * stable-3.11: Prevent the synchronous replication of create-refs via apply-object Flag ref-updates events creating a new ref Fix the create/delete of ref-specs in FetchOne delta Report deletions as succeeded in the fetch-ref-replicated events Change-Id: I65c2b8e161dd5b165fd2929c6861aa34e8d71d35
This plugin can automatically mirror repositories from other systems.
Typically replication should be done over SSH, with a passwordless public/private key pair. On a trusted network it is also possible to use replication over the insecure (but much faster due to no authentication overhead or encryption) git:// protocol, by enabling the upload-pack service on the receiving system, but this configuration is not recommended. It is also possible to specify a local path as replication source. This makes sense if a network share is mounted to which the repositories should be replicated from.
To be allowed to trigger pull replication a user must be a member of a group that is granted the ‘Pull Replication’ capability (provided by this plugin) or the ‘Administrate Server’ capability.
Changes will be automatically indexed upon replication.
For more information please refer to the docs