List for cgit developers and users
 help / color / mirror / Atom feed
From: june at causal.agency (June Bug)
Subject: Dumb HTTP & Caching
Date: Sat, 11 Apr 2020 18:08:17 -0400	[thread overview]
Message-ID: <258A3E64-E0CF-414D-82F5-012B8270B324@causal.agency> (raw)
In-Reply-To: <5ab1e63c-b58e-b2c0-f650-224028201577@necoro.eu>


> On Apr 11, 2020, at 17:59, Ren? Neumann <lists at necoro.eu> 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
<https://text.causal.agency/007-cgit-setup.txt>, ?Update: fast HTTPS
clones?.


      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:
  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=258A3E64-E0CF-414D-82F5-012B8270B324@causal.agency \
    --to=cgit@lists.zx2c4.com \
    /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).