My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 496: Use a persistent configuration file for gerrit's Jetty CGI servlet for gitweb
1 person starred this issue and may be notified of changes. Back to list
Status:  Released
Owner:  ----
Closed:  Mar 2012


Sign in to add a comment
 
Reported by mike.lifeguard@gmail.com, Mar 13, 2010
This currently uses a temp file generated by gerrit in /tmp (or whatever)
which is not persistent. Instead, a configuration file for gitweb should be
generated in $site_path/etc so it remains after reboot for example (some
systems wipe /tmp). If necessary, this might use two files, one which
shouldn't be edited (the temp file gerrit generates says to not edit it).
Mar 13, 2010
#1 sop@google.com
I really don't want do this.  Configuration of Gerrit and
anything it uses is driven from Git style config files in
$site_dir/etc.  I want to keep that consistent, so if we
are in fact wrapping around gitweb, we should be filling
out as much of that Perl configuration as possible based
on our gerrit.config, and what's left, we should export
as features in gerrit.config.

However.  There is an undocumented thing here, we do in
fact load $site_path/etc/gitweb_config.perl and allow it
to override prior configuration.

So I guess I've already done what you asked for, I just
didn't document it.  *sigh*
Status: Accepted
Mar 13, 2010
#2 sop@google.com
Documented in I1756d268e111d0021ebb8d8f248fd7e374ef49b4
Status: Fixed
Labels: Milestone-2.1.2.1
Mar 27, 2012
#3 sop@google.com
(No comment was entered for this change.)
Status: Released
Sign in to add a comment

Powered by Google Project Hosting