List for cgit developers and users
 help / color / mirror / Atom feed
From: june at (June Bug)
Subject: Dumb HTTP & Caching
Date: Sat, 11 Apr 2020 18:08:17 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> On Apr 11, 2020, at 17:59, Ren? Neumann <lists at> wrote:
> Hi,
> I'm using cgit as a dumb HTTP frontend to my git repositories. And I noticed that sometimes git push (via ssh) followed by git pull (via https) will return the revision before the push.
> Is it possible, that cgit's caching interferes with pull here? If so, is there some way to turn it off without disabling caching as a whole?

That does seem to be the case in my experience too. I suggest setting
up the ?smart? HTTP transport git-http-backend in parallel with
cgit, which also greatly improves pull/clone speed. You can see how
I set it up in the last section of
<>, ?Update: fast HTTPS

      reply	other threads:[~2020-04-11 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11 21:59 
2020-04-11 22:08 ` june [this message]

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:

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

  git send-email \ \ \
    --subject='Re: Dumb HTTP & Caching' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).