| commit | f426afbc98efb346538d26cf08cdaafd75827060 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Sat Feb 22 12:48:50 2025 +0000 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Sat Feb 22 04:54:09 2025 -0800 |
| tree | f2960601409545094625c1e3e0a77a51246d7b81 | |
| parent | fbe3b345424c021df76d0982eef1786ba815829d [diff] |
Move ProjectDeletionAction/CacheDeleteHandler PullReplicationModule Following I31cb7378ba7a the classes responsible for providing the delete project functionality need to be moved to PullReplicationModule as it is used also in the stream event listener and therefore used even without the HTTP REST-APIs. Having the binding in the HttpModule caused two conflicting bindings, one done just-in-time indirectly by the StreamEventListener and another one explicitly bound in the PullReplicationModule which was making the plugin failing to load because of a double binding. Change-Id: I9dd29693ee48851a45bff79078f7de27d7c631fc
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