git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 30 Dec 2008 14:37:44 -0800 (PST)	[thread overview]
Message-ID: <m3sko5b84t.fsf@localhost.localdomain> (raw)
In-Reply-To: <9B3762519053E645820D9CEBD18B3734023A9FBA00@XEDAMAIL2.ex.ad3.ucdavis.edu>

Thomas Amsler <tpamsler@ucdavis.edu> writes:

> Hello,
> 
> I am trying to get the gitweb $export_ok to work. According the
> installation instructions:
> 
>   Alternatively, you can configure gitweb to only list and allow
>   viewing of the explicitly exported repositories, via the
>   GITWEB_EXPORT_OK build configuration variable (or the $export_ok
>   variable in gitweb config file). If it evaluates to true, gitweb
>   shows repositories only if this file exists in its object database
>   (if directory has the magic file named $export_ok).
> 
> ... I set $export_ok = "true" in my /etc/gitweb.conf file.
[...]

$export_ok is not a boolean, is the _name_ of a file, which if it
is present, then repository is exported to gitweb, and if it is not,
it is invisible to gitweb. It means that if for example we have
  $export_ok = "gitweb-export-ok";
in the GITWEB_CONFIG file (usually gitweb_config.perl, installed
in the same place as gitweb.cgi), the repo.git is exported only
if it has file gitweb-export-ok in it.

This mechanism is similar to git-daemon and its magic file
"git-daemon-export-ok".

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2008-12-30 22:39 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 [this message]
2008-12-30 23:02   ` Jakub Narebski
     [not found]   ` <6db6bed70812302037w54fe5640of234cd611f5ab45e@mail.gmail.com>
2008-12-31  9:00     ` Jakub Narebski
     [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=m3sko5b84t.fsf@localhost.localdomain \
    --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).