From: john at keeping.me.uk (John Keeping)
Subject: Can I get detailed Cgit logs?
Date: Tue, 25 Feb 2014 19:29:08 +0000 [thread overview]
Message-ID: <20140225192908.GC18371@serenity.lan> (raw)
In-Reply-To: <530CEDD2.90207@thewordnerd.info>
On Tue, Feb 25, 2014 at 01:24:02PM -0600, Nolan Darilek wrote:
> OK, figured it out. I was proxying to the Cgit docker container via
> Nginx, and specified:
>
> proxy_pass http://cgit.prod.docker;
>
> instead of:
>
> proxy_pass http://cgit.prod.docker/;
>
> Maybe some sort of "debug mode" might have helped diagnose the issue?
> Presumably Cgit was looking for repositories in a directory that didn't
> exist. Having a way to output "No repositories found in
> /srv/git/doesnotexist" might have helped me track that down more
> quickly. Or maybe such a thing exists and my Google powers are weak. :)
CGit does log "Error opening directory" if either the directory
specified to scan does not exist or a directory listed in the project
list does not exist.
next prev parent reply other threads:[~2014-02-25 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 17:53 nolan
2014-02-25 18:08 ` john
2014-02-25 18:40 ` nolan
2014-02-25 19:24 ` nolan
2014-02-25 19:29 ` john [this message]
2014-02-25 19:25 ` john
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=20140225192908.GC18371@serenity.lan \
--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).