From: Jakub Narebski <jnareb@gmail.com>
To: "Thomas Amsler" <tpamsler@ucdavis.edu>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: gitweb $export_ok question
Date: Wed, 31 Dec 2008 10:00:21 +0100 [thread overview]
Message-ID: <200812311000.25818.jnareb@gmail.com> (raw)
In-Reply-To: <6db6bed70812302037w54fe5640of234cd611f5ab45e@mail.gmail.com>
Thomas Amsler wrote:
> Thank you for your information.
>
> I have just tried that but the repository doesn't show up in gitweb
>
> - added to /etc/gitweb.conf
> -- $export_ok = "gitweb-export-ok"
> - touched the "gitweb-export-ok" file in the repository
> -- touch /path-to-repo/repository/authz.git/gitweb-export-ok
>
> Then gitweb reports:
>
> 404 - No projects found
>
> Does the gitweb-export-ok file need to be part of the repo so that it is
> tracked?
No, gitweb-export-ok file has to be in $GIT_DIR (like description file),
not part of repo.
As to "No projects found" error: what is your $projectroot? Is it
either "/path-to-repo/repository" or "/path-to-repo"? Is repository
readable and searchable for the web server user (does it have correct
permissions)?
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-12-31 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 20:26 gitweb $export_ok question Thomas Amsler
2008-12-30 22:37 ` Jakub Narebski
2008-12-30 23:02 ` Jakub Narebski
[not found] ` <6db6bed70812302037w54fe5640of234cd611f5ab45e@mail.gmail.com>
2008-12-31 9:00 ` Jakub Narebski [this message]
[not found] ` <6db6bed70812311013l3cf575c1y874e71e70d1dde57@mail.gmail.com>
2008-12-31 18:56 ` Thomas Amsler
[not found] ` <6db6bed70812311027g3be1cfbei35c014243237fd59@mail.gmail.com>
2009-01-01 22:51 ` Jakub Narebski
2009-01-03 13:23 ` [PATCH] gitweb: Document that gitweb deals with bare repositories Jakub Narebski
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=200812311000.25818.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=tpamsler@ucdavis.edu \
/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).