Re: Synchronous replication on push
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Nov 2, 2024, 14:49 UTC
- Message-ID
- <ZyY74N_NjmaJ2677@tapette.crustytoothpaste.net>
- In-Reply-To
- <20241102133511.6375B609AC@jupiter.mumble.net>
On 2024-11-02 at 13:35:11, Taylor R Campbell wrote:
Show 5 quoted lines
> I'm asking about how to configure a _single_ frontend remote, from the > perspective of developers who are pushing from their development > workstations, so that it replicates to one or many backend stores. > This is, for example, the usage model of Github's proprietary > implementation.
I don't think there's built-in functionality for this and I'm not sure that it can be done without additional software.
If you really wanted to try to do this with out of the box Git, you could create a `pre-receive` hook that did policy controls and then on success, took all of the objects from the quarantine and rsynced them (without overwriting) to the remote store, and then use the `reference-transaction` hook to replicate the reference transaction to the remote side via SSH or something. I haven't tested this, so it might or might not work, but you could try it.
Note that GitHub has a separate service that does the replication and intercepts the ref update to send it through the three-phase commit, so they don't rely on features of core Git to implement this functionality.
-- brian m. carlson (they/them or he/him) Toronto, Ontario, CA