git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor R Campbell <git@campbell.mumble.net>
To: "Matěj Cepl" <mcepl@cepl.eu>
Cc: git@vger.kernel.org
Subject: Re: Synchronous replication on push
Date: Sat, 2 Nov 2024 13:35:11 +0000	[thread overview]
Message-ID: <20241102133511.6375B609AC@jupiter.mumble.net> (raw)
In-Reply-To: <D5BM0CBSPT9I.97E2CAX9DE17@cepl.eu> (mcepl@cepl.eu)

> Date: Sat, 02 Nov 2024 11:09:52 +0100
> From: Matěj Cepl <mcepl@cepl.eu>
> 
> On Sat Nov 2, 2024 at 3:06 AM CET, Taylor R Campbell wrote:
> > Suppose I have a front end repository:
> >
> > user@frontend.example.com:/repo.git
> >
> > Whenever I push anything to it, I want the push -- that is, all the
> > objects, and all the ref updates -- to be synchronously replicated to
> > another remote repository, the back end:
> >
> > git@backend.example.com:/repo.git
> 
> https://stackoverflow.com/q/14290113/164233

Thanks, but that is about how to configure my local repository to use
multiple remotes for a single git push command, which is not what I'm
asking about.

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.

  reply	other threads:[~2024-11-02 13:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-02  2:06 Synchronous replication on push Taylor R Campbell
2024-11-02 10:09 ` Matěj Cepl
2024-11-02 13:35   ` Taylor R Campbell [this message]
2024-11-02 14:49     ` brian m. carlson
2024-11-04 13:35       ` Taylor R Campbell
2024-11-04 14:40         ` Konstantin Ryabitsev
2024-11-04 15:50           ` Taylor R Campbell
2024-11-04 22:36         ` brian m. carlson
2024-11-04 23:47 ` Jeff King
2024-11-05  1:34   ` Taylor R Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241102133511.6375B609AC@jupiter.mumble.net \
    --to=git@campbell.mumble.net \
    --cc=git@vger.kernel.org \
    --cc=mcepl@cepl.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).