e31d02c9cd
Now that the 2.x code base is over a year old, and has been in production for almost a full year, its time to stop calling this 'Gerrit2' and start referring to it by the complete project name, Gerrit Code Review. Change-Id: Ifb37dd63b94ed7e1b938511aa0fc2a6ad3c981d6 Signed-off-by: Shawn O. Pearce <sop@google.com>
46 lines
1.3 KiB
Plaintext
46 lines
1.3 KiB
Plaintext
Gerrit Code Review - Gitweb Integration
|
|
=======================================
|
|
|
|
Gerrit Code Review can generate hyperlinks to gitweb, allowing users
|
|
to jump from Gerrit content to the same information, but shown by
|
|
gitweb.
|
|
|
|
To enable the gitweb integration, set gitweb.url with the URL of
|
|
your gitweb CGI.
|
|
|
|
The CGI's `$projectroot` should be the same directory as
|
|
gerrit.basePath, or a fairly current replica. If a replica is
|
|
being used, ensure it uses a full mirror, so the `refs/changes/*`
|
|
namespace is available.
|
|
|
|
====
|
|
git config --file $site_path/etc/gerrit.config gitweb.url http://example.com/gitweb.cgi
|
|
====
|
|
|
|
After updating `'$site_path'/etc/gerrit.config`, the Gerrit server must
|
|
be restarted and clients must reload the host page to see the change.
|
|
|
|
Access Control
|
|
--------------
|
|
|
|
Gitweb access controls can be implemented using standard web server
|
|
access controls. This isn't typically integrated with Gerrit's own
|
|
access controls. Caution must be taken to ensure the controls are
|
|
consistent if access needs to be restricted.
|
|
|
|
Caching Gitweb
|
|
--------------
|
|
|
|
If your repository set is large and you are expecting a lot
|
|
of users, you may want to look at the caching forks used by
|
|
high-traffic sites like kernel.org or repo.or.cz.
|
|
|
|
See Also
|
|
--------
|
|
|
|
* link:config-gerrit.html#gitweb[Section gitweb]
|
|
|
|
GERRIT
|
|
------
|
|
Part of link:index.html[Gerrit Code Review]
|