diff options
| author | Junio C Hamano <gitster@pobox.com> | 2014-10-31 13:25:53 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2014-10-31 13:25:53 -0700 |
| commit | c14e6ad9a230ad90c84b7f620d87fbe49a2d0342 (patch) | |
| tree | 120346dc383e3d1c4219fe8c533eb22cb6af2b55 /gitweb.conf.html | |
| parent | 2a4bcbc355496c8d83b1b9f8892c4cbe8f584158 (diff) | |
| download | git-htmldocs-c14e6ad9a230ad90c84b7f620d87fbe49a2d0342.tar.gz | |
Autogenerated HTML docs for v2.2.0-rc0
Diffstat (limited to 'gitweb.conf.html')
| -rw-r--r-- | gitweb.conf.html | 320 |
1 files changed, 159 insertions, 161 deletions
diff --git a/gitweb.conf.html b/gitweb.conf.html index ad204e30e..91c65362d 100644 --- a/gitweb.conf.html +++ b/gitweb.conf.html @@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.6" />
+<meta name="generator" content="AsciiDoc 8.6.9" />
<title>gitweb.conf(5)</title>
<style type="text/css">
/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
@@ -87,10 +87,16 @@ ul, ol, li > p { ul > li { color: #aaa; }
ul > li > * { color: black; }
-pre {
+.monospaced, code, pre {
+ font-family: "Courier New", Courier, monospace;
+ font-size: inherit;
+ color: navy;
padding: 0;
margin: 0;
}
+pre {
+ white-space: pre-wrap;
+}
#author {
color: #527bbd;
@@ -219,7 +225,7 @@ div.exampleblock > div.content { }
div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
+span.image img { border-style: none; vertical-align: text-bottom; }
a.image:visited { color: white; }
dl {
@@ -349,7 +355,7 @@ div.colist td img { margin-bottom: 0.1em;
}
-div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
margin-top: 0;
margin-bottom: 0;
}
@@ -407,18 +413,14 @@ span.underline { text-decoration: underline; } span.overline { text-decoration: overline; }
span.line-through { text-decoration: line-through; }
+div.unbreakable { page-break-inside: avoid; }
+
/*
* xhtml11 specific
*
* */
-tt {
- font-family: monospace;
- font-size: inherit;
- color: navy;
-}
-
div.tableblock {
margin-top: 1.0em;
margin-bottom: 1.5em;
@@ -452,12 +454,6 @@ div.tableblock > table[frame="vsides"] { *
* */
-.monospaced {
- font-family: monospace;
- font-size: inherit;
- color: navy;
-}
-
table.tableblock {
margin-top: 1.0em;
margin-bottom: 1.5em;
@@ -537,6 +533,8 @@ body.manpage div.sectionbody { @media print {
body.manpage div#toc { display: none; }
}
+
+
</style>
<script type="text/javascript">
/*<+'])');
+ var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
// Function that scans the DOM tree for header elements (the DOM2
// nodeIterator API would be a better technique but not supported by all
// browsers).
@@ -610,7 +608,7 @@ toc: function (toclevels) { var i;
for (i = 0; i < toc.childNodes.length; i++) {
var entry = toc.childNodes[i];
- if (entry.nodeName == 'div'
+ if (entry.nodeName.toLowerCase() == 'div'
&& entry.getAttribute("class")
&& entry.getAttribute("class").match(/^toclevel/))
tocEntriesToRemove.push(entry);
@@ -656,7 +654,7 @@ footnotes: function () { var entriesToRemove = [];
for (i = 0; i < noteholder.childNodes.length; i++) {
var entry = noteholder.childNodes[i];
- if (entry.nodeName == 'div' && entry.getAttribute("class") == "footnote")
+ if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
entriesToRemove.push(entry);
}
for (i = 0; i < entriesToRemove.length; i++) {
@@ -757,15 +755,15 @@ gitweb.conf(5) Manual Page <div class="sectionbody">
<div class="paragraph"><p>The gitweb CGI script for viewing Git repositories over the web uses a
perl script fragment as its configuration file. You can set variables
-using "<tt>our $variable = value</tt>"; text from a "#" character until the
+using "<code>our $variable = value</code>"; text from a "#" character until the
end of a line is ignored. See <strong>perlsyn</strong>(1) for details.</p></div>
<div class="paragraph"><p>An example:</p></div>
<div class="literalblock">
<div class="content">
-<pre><tt># gitweb configuration file for http://git.example.org
+<pre><code># gitweb configuration file for http://git.example.org
#
our $projectroot = "/srv/git"; # FHS recommendation
-our $site_name = 'Example.org >> Repos';</tt></pre>
+our $site_name = 'Example.org >> Repos';</code></pre>
</div></div>
<div class="paragraph"><p>The configuration file is used to override the default settings that
were built into gitweb at the time the <em>gitweb.cgi</em> script was generated.</p></div>
@@ -810,16 +808,16 @@ in the above sequence.</p></div> <div class="paragraph"><p>Locations of the common system-wide configuration file, the fallback
system-wide configuration file and the per-instance configuration file
are defined at compile time using build-time Makefile configuration
-variables, respectively <tt>GITWEB_CONFIG_COMMON</tt>, <tt>GITWEB_CONFIG_SYSTEM</tt>
-and <tt>GITWEB_CONFIG</tt>.</p></div>
+variables, respectively <code>GITWEB_CONFIG_COMMON</code>, <code>GITWEB_CONFIG_SYSTEM</code>
+and <code>GITWEB_CONFIG</code>.</p></div>
<div class="paragraph"><p>You can also override locations of gitweb configuration files during
runtime by setting the following environment variables:
-<tt>GITWEB_CONFIG_COMMON</tt>, <tt>GITWEB_CONFIG_SYSTEM</tt> and <tt>GITWEB_CONFIG</tt>
+<code>GITWEB_CONFIG_COMMON</code>, <code>GITWEB_CONFIG_SYSTEM</code> and <code>GITWEB_CONFIG</code>
to a non-empty value.</p></div>
<div class="paragraph"><p>The syntax of the configuration files is that of Perl, since these files are
handled by sourcing them as fragments of Perl code (the language that
gitweb itself is written in). Variables are typically set using the
-<tt>our</tt> qualifier (as in "<tt>our $variable = <value>;</tt>") to avoid syntax
+<code>our</code> qualifier (as in "<code>our $variable = <value>;</code>") to avoid syntax
errors if a new version of gitweb no longer uses a variable and therefore
stops declaring it.</p></div>
<div class="paragraph"><p>You can include other configuration file using read_config_file()
@@ -829,7 +827,7 @@ of Git repository management tools) in a separate file, e.g. in <em>/etc/gitweb-gitolite.conf</em>. To include it, put</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>read_config_file("/etc/gitweb-gitolite.conf");</tt></pre>
+<pre><code>read_config_file("/etc/gitweb-gitolite.conf");</code></pre>
</div></div>
<div class="paragraph"><p>somewhere in gitweb configuration file used, e.g. in per-installation
gitweb configuration file. Note that read_config_file() checks itself
@@ -839,7 +837,7 @@ It also handles errors in included file.</p></div> perfectly well for some installations. Still, a configuration file is
useful for customizing or tweaking the behavior of gitweb in many ways, and
some optional features will not be present unless explicitly enabled using
-the configurable <tt>%features</tt> variable (see also "Configuring gitweb
+the configurable <code>%features</code> variable (see also "Configuring gitweb
features" section below).</p></div>
</div>
</div>
@@ -862,25 +860,25 @@ $projectroot <dd>
<p>
Absolute filesystem path which will be prepended to project path;
- the path to repository is <tt>$projectroot/$project</tt>. Set to
- <tt>$GITWEB_PROJECTROOT</tt> during installation. This variable has to be
+ the path to repository is <code>$projectroot/$project</code>. Set to
+ <code>$GITWEB_PROJECTROOT</code> during installation. This variable has to be
set correctly for gitweb to find repositories.
</p>
-<div class="paragraph"><p>For example, if <tt>$projectroot</tt> is set to "/srv/git" by putting the following
+<div class="paragraph"><p>For example, if <code>$projectroot</code> is set to "/srv/git" by putting the following
in gitweb config file:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>our $projectroot = "/srv/git";</tt></pre>
+<pre><code>our $projectroot = "/srv/git";</code></pre>
</div></div>
<div class="paragraph"><p>then</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>http://git.example.com/gitweb.cgi?p=foo/bar.git</tt></pre>
+<pre><code>http://git.example.com/gitweb.cgi?p=foo/bar.git</code></pre>
</div></div>
<div class="paragraph"><p>and its path_info based equivalent</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>http://git.example.com/gitweb.cgi/foo/bar.git</tt></pre>
+<pre><code>http://git.example.com/gitweb.cgi/foo/bar.git</code></pre>
</div></div>
<div class="paragraph"><p>will map to the path <em>/srv/git/foo/bar.git</em> on the filesystem.</p></div>
</dd>
@@ -896,28 +894,28 @@ $projects_list having the following format</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt><URI-encoded filesystem path to repository> SP <URI-encoded repository owner></tt></pre>
+<pre><code><URI-encoded filesystem path to repository> SP <URI-encoded repository owner></code></pre>
</div></div>
-<div class="paragraph"><p>The default value of this variable is determined by the <tt>GITWEB_LIST</tt>
+<div class="paragraph"><p>The default value of this variable is determined by the <code>GITWEB_LIST</code>
makefile variable at installation time. If this variable is empty, gitweb
-will fall back to scanning the <tt>$projectroot</tt> directory for repositories.</p></div>
+will fall back to scanning the <code>$projectroot</code> directory for repositories.</p></div>
</dd>
<dt class="hdlist1">
$project_maxdepth
</dt>
<dd>
<p>
- If <tt>$projects_list</tt> variable is unset, gitweb will recursively
- scan filesystem for Git repositories. The <tt>$project_maxdepth</tt>
- is used to limit traversing depth, relative to <tt>$projectroot</tt>
+ If <code>$projects_list</code> variable is unset, gitweb will recursively
+ scan filesystem for Git repositories. The <code>$project_maxdepth</code>
+ is used to limit traversing depth, relative to <code>$projectroot</code>
(starting point); it means that directories which are further
- from <tt>$projectroot</tt> than <tt>$project_maxdepth</tt> will be skipped.
+ from <code>$projectroot</code> than <code>$project_maxdepth</code> will be skipped.
</p>
<div class="paragraph"><p>It is purely performance optimization, originally intended for MacOS X,
where recursive directory traversal is slow. Gitweb follows symbolic
links, but it detects cycles, ignoring any duplicate files and directories.</p></div>
<div class="paragraph"><p>The default value of this variable is determined by the build-time
-configuration variable <tt>GITWEB_PROJECT_MAXDEPTH</tt>, which defaults to
+configuration variable <code>GITWEB_PROJECT_MAXDEPTH</code>, which defaults to
2007.</p></div>
</dd>
<dt class="hdlist1">
@@ -927,9 +925,9 @@ $export_ok <p>
Show repository only if this file exists (in repository). Only
effective if this variable evaluates to true. Can be set when
- building gitweb by setting <tt>GITWEB_EXPORT_OK</tt>. This path is
- relative to <tt>GIT_DIR</tt>. git-daemon[1] uses <em>git-daemon-export-ok</em>,
- unless started with <tt>--export-all</tt>. By default this variable is
+ building gitweb by setting <code>GITWEB_EXPORT_OK</code>. This path is
+ relative to <code>GIT_DIR</code>. git-daemon[1] uses <em>git-daemon-export-ok</em>,
+ unless started with <code>--export-all</code>. By default this variable is
not set, which means that this feature is turned off.
</p>
</dd>
@@ -947,12 +945,12 @@ $export_auth_hook </p>
<div class="listingblock">
<div class="content">
-<pre><tt>our $export_auth_hook = sub { return -e "$_[0]/git-daemon-export-ok"; };</tt></pre>
+<pre><code>our $export_auth_hook = sub { return -e "$_[0]/git-daemon-export-ok"; };</code></pre>
</div></div>
-<div class="paragraph"><p>though the above might be done by using <tt>$export_ok</tt> instead</p></div>
+<div class="paragraph"><p>though the above might be done by using <code>$export_ok</code> instead</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>our $export_ok = "git-daemon-export-ok";</tt></pre>
+<pre><code>our $export_ok = "git-daemon-export-ok";</code></pre>
</div></div>
<div class="paragraph"><p>If not set (default), it means that this feature is disabled.</p></div>
<div class="paragraph"><p>See also more involved example in "Controlling access to Git repositories"
@@ -964,11 +962,11 @@ $strict_export <dd>
<p>
Only allow viewing of repositories also shown on the overview page.
- This for example makes <tt>$gitweb_export_ok</tt> file decide if repository is
- available and not only if it is shown. If <tt>$gitweb_list</tt> points to
+ This for example makes <code>$gitweb_export_ok</code> file decide if repository is
+ available and not only if it is shown. If <code>$gitweb_list</code> points to
file with list of project, only those repositories listed would be
available for gitweb. Can be set during building gitweb via
- <tt>GITWEB_STRICT_EXPORT</tt>. By default this variable is not set, which
+ <code>GITWEB_STRICT_EXPORT</code>. By default this variable is not set, which
means that you can directly access those repositories that are hidden
from projects list page (e.g. the are not listed in the $projects_list
file).
@@ -986,8 +984,8 @@ $GIT </dt>
<dd>
<p>
- Core git executable to use. By default set to <tt>$GIT_BINDIR/git</tt>, which
- in turn is by default set to <tt>$(bindir)/git</tt>. If you use Git installed
+ Core git executable to use. By default set to <code>$GIT_BINDIR/git</code>, which
+ in turn is by default set to <code>$(bindir)/git</code>. If you use Git installed
from a binary package, you should usually set this to "/usr/bin/git".
This can just be "git" if your web server has a sensible PATH; from
security point of view it is better to use absolute path to git binary.
@@ -1022,19 +1020,19 @@ $highlight_bin use syntax highlighting.
</p>
<div class="paragraph"><p><strong>NOTE</strong>: if you want to add support for new file type (supported by
-"highlight" but not used by gitweb), you need to modify <tt>%highlight_ext</tt>
-or <tt>%highlight_basename</tt>, depending on whether you detect type of file
+"highlight" but not used by gitweb), you need to modify <code>%highlight_ext</code>
+or <code>%highlight_basename</code>, depending on whether you detect type of file
based on extension (for example "sh") or on its basename (for example
"Makefile"). The keys of these hashes are extension and basename,
respectively, and value for given key is name of syntax to be passed via
-<tt>--syntax <syntax></tt> to highlighter.</p></div>
+<code>--syntax <syntax></code> to highlighter.</p></div>
<div class="paragraph"><p>For example if repositories you are hosting use "phtml" extension for
PHP files, and you want to have correct syntax-highlighting for those
files, you can add the following to gitweb configuration:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>our %highlight_ext;
-$highlight_ext{'phtml'} = 'php';</tt></pre>
+<pre><code>our %highlight_ext;
+$highlight_ext{'phtml'} = 'php';</code></pre>
</div></div>
</dd>
</dl></div>
@@ -1044,7 +1042,7 @@ $highlight_ext{'phtml'} = 'php';</tt></pre> <div class="paragraph"><p>The configuration variables described below configure some of gitweb links:
their target and their look (text or image), and where to find page
prerequisites (stylesheet, favicon, images, scripts). Usually they are left
-at their default values, with the possible exception of <tt>@stylesheets</tt>
+at their default values, with the possible exception of <code>@stylesheets</code>
variable.</p></div>
<div class="dlist"><dl>
<dt class="hdlist1">
@@ -1056,21 +1054,21 @@ variable.</p></div> might specify more than one stylesheet, for example to use "gitweb.css"
as base with site specific modifications in a separate stylesheet
to make it easier to upgrade gitweb. For example, you can add
- a <tt>site</tt> stylesheet by putting
+ a <code>site</code> stylesheet by putting
</p>
<div class="listingblock">
<div class="content">
-<pre><tt>push @stylesheets, "gitweb-site.css";</tt></pre>
+<pre><code>push @stylesheets, "gitweb-site.css";</code></pre>
</div></div>
<div class="paragraph"><p>in the gitweb config file. Those values that are relative paths are
relative to base URI of gitweb.</p></div>
<div class="paragraph"><p>This list should contain the URI of gitweb’s standard stylesheet. The default
-URI of gitweb stylesheet can be set at build time using the <tt>GITWEB_CSS</tt>
+URI of gitweb stylesheet can be set at build time using the <code>GITWEB_CSS</code>
makefile variable. Its default value is <em>static/gitweb.css</em>
-(or <em>static/gitweb.min.css</em> if the <tt>CSSMIN</tt> variable is defined,
+(or <em>static/gitweb.min.css</em> if the <code>CSSMIN</code> variable is defined,
i.e. if CSS minifier is used during build).</p></div>
-<div class="paragraph"><p><strong>Note</strong>: there is also a legacy <tt>$stylesheet</tt> configuration variable, which was
-used by older gitweb. If <tt>$stylesheet</tt> variable is defined, only CSS stylesheet
+<div class="paragraph"><p><strong>Note</strong>: there is also a legacy <code>$stylesheet</code> configuration variable, which was
+used by older gitweb. If <code>$stylesheet</code> variable is defined, only CSS stylesheet
given by this variable is used by gitweb.</p></div>
</dd>
<dt class="hdlist1">
@@ -1082,7 +1080,7 @@ $logo server, or to be more the generic URI of logo, 72x27 size). This image
is displayed in the top right corner of each gitweb page and used as
a logo for the Atom feed. Relative to the base URI of gitweb (as a path).
- Can be adjusted when building gitweb using <tt>GITWEB_LOGO</tt> variable
+ Can be adjusted when building gitweb using <code>GITWEB_LOGO</code> variable
By default set to <em>static/git-logo.png</em>.
</p>
</dd>
@@ -1096,7 +1094,7 @@ $favicon as "image/png" type. Web browsers that support favicons (website icons)
may display them in the browser’s URL bar and next to the site name in
bookmarks. Relative to the base URI of gitweb. Can be adjusted at
- build time using <tt>GITWEB_FAVICON</tt> variable.
+ build time using <code>GITWEB_FAVICON</code> variable.
By default set to <em>static/git-favicon.png</em>.
</p>
</dd>
@@ -1108,10 +1106,10 @@ $javascript Points to the location where you put <em>gitweb.js</em> on your web server,
or to be more generic the URI of JavaScript code used by gitweb.
Relative to the base URI of gitweb. Can be set at build time using
- the <tt>GITWEB_JS</tt> build-time configuration variable.
+ the <code>GITWEB_JS</code> build-time configuration variable.
</p>
<div class="paragraph"><p>The default value is either <em>static/gitweb.js</em>, or <em>static/gitweb.min.js</em> if
-the <tt>JSMIN</tt> build variable was defined, i.e. if JavaScript minifier was used
+the <code>JSMIN</code> build variable was defined, i.e. if JavaScript minifier was used
at build time. <strong>Note</strong> that this single file is generated from multiple
individual JavaScript "modules".</p></div>
</dd>
@@ -1122,7 +1120,7 @@ $home_link <p>
Target of the home link on the top of all pages (the first part of view
"breadcrumbs"). By default it is set to the absolute URI of a current page
- (to the value of <tt>$my_uri</tt> variable, or to "/" if <tt>$my_uri</tt> is undefined
+ (to the value of <code>$my_uri</code> variable, or to "/" if <code>$my_uri</code> is undefined
or is an empty string).
</p>
</dd>
@@ -1131,11 +1129,11 @@ $home_link_str </dt>
<dd>
<p>
- Label for the "home link" at the top of all pages, leading to <tt>$home_link</tt>
+ Label for the "home link" at the top of all pages, leading to <code>$home_link</code>
(usually the main gitweb page, which contains the projects list). It is
used as the first component of gitweb’s "breadcrumb trail":
- <tt><home link> / <project> / <action></tt>. Can be set at build time using
- the <tt>GITWEB_HOME_LINK_STR</tt> variable. By default it is set to "projects",
+ <code><home link> / <project> / <action></code>. Can be set at build time using
+ the <code>GITWEB_HOME_LINK_STR</code> variable. By default it is set to "projects",
as this link leads to the list of projects. Another popular choice is to
set it to the name of site. Note that it is treated as raw HTML so it
should not be set from untrusted sources.
@@ -1150,8 +1148,8 @@ $home_link_str the home link, to pages that are logically "above" the gitweb projects
list, such as the organization and department which host the gitweb
server. Each element of the list is a reference to an array, in which
- element 0 is the link text (equivalent to <tt>$home_link_str</tt>) and element
- 1 is the target URL (equivalent to <tt>$home_link</tt>).
+ element 0 is the link text (equivalent to <code>$home_link_str</code>) and element
+ 1 is the target URL (equivalent to <code>$home_link</code>).
</p>
<div class="paragraph"><p>For example, the following setting produces a breadcrumb trail like
"home / dev / projects / …" where "projects" is the home link.</p></div>
@@ -1159,10 +1157,10 @@ $home_link_str </dl></div>
<div class="listingblock">
<div class="content">
-<pre><tt> our @extra_breadcrumbs = (
+<pre><code> our @extra_breadcrumbs = (
[ 'home' => 'https://www.example.org/' ],
[ 'dev' => 'https://dev.example.org/' ],
- );</tt></pre>
+ );</code></pre>
</div></div>
<div class="dlist"><dl>
<dt class="hdlist1">
@@ -1195,12 +1193,12 @@ $site_name <p>
Name of your site or organization, to appear in page titles. Set it
to something descriptive for clearer bookmarks etc. If this variable
- is not set or is, then gitweb uses the value of the <tt>SERVER_NAME</tt>
+ is not set or is, then gitweb uses the value of the <code>SERVER_NAME</code>
CGI environment variable, setting site name to "$SERVER_NAME Git",
or "Untitled Git" if this variable is not set (e.g. if running gitweb
as standalone script).
</p>
-<div class="paragraph"><p>Can be set using the <tt>GITWEB_SITENAME</tt> at build time. Unset by default.</p></div>
+<div class="paragraph"><p>Can be set using the <code>GITWEB_SITENAME</code> at build time. Unset by default.</p></div>
</dd>
<dt class="hdlist1">
$site_html_head_string
@@ -1208,7 +1206,7 @@ $site_html_head_string <dd>
<p>
HTML snippet to be included in the <head> section of each page.
- Can be set using <tt>GITWEB_SITE_HTML_HEAD_STRING</tt> at build time.
+ Can be set using <code>GITWEB_SITE_HTML_HEAD_STRING</code> at build time.
No default value.
</p>
</dd>
@@ -1219,7 +1217,7 @@ $site_header <p>
Name of a file with HTML to be included at the top of each page.
Relative to the directory containing the <em>gitweb.cgi</em> script.
- Can be set using <tt>GITWEB_SITE_HEADER</tt> at build time. No default
+ Can be set using <code>GITWEB_SITE_HEADER</code> at build time. No default
value.
</p>
</dd>
@@ -1230,7 +1228,7 @@ $site_footer <p>
Name of a file with HTML to be included at the bottom of each page.
Relative to the directory containing the <em>gitweb.cgi</em> script.
- Can be set using <tt>GITWEB_SITE_FOOTER</tt> at build time. No default
+ Can be set using <code>GITWEB_SITE_FOOTER</code> at build time. No default
value.
</p>
</dd>
@@ -1242,7 +1240,7 @@ $home_text Name of a HTML file which, if it exists, is included on the
gitweb projects overview page ("projects_list" view). Relative to
the directory containing the gitweb.cgi script. Default value
- can be adjusted during build time using <tt>GITWEB_HOMETEXT</tt> variable.
+ can be adjusted during build time using <code>GITWEB_HOMETEXT</code> variable.
By default set to <em>indextext.html</em>.
</p>
</dd>
@@ -1267,7 +1265,7 @@ $default_projects_order means the ordering used if you don’t explicitly sort projects list
(if there is no "o" CGI query parameter in the URL). Valid values
are "none" (unsorted), "project" (projects are by project name,
- i.e. path to repository relative to <tt>$projectroot</tt>), "descr"
+ i.e. path to repository relative to <code>$projectroot</code>), "descr"
(project description), "owner", and "age" (by date of most current
commit).
</p>
@@ -1287,7 +1285,7 @@ $default_blob_plain_mimetype Default mimetype for the blob_plain (raw) view, if mimetype checking
doesn’t result in some other type; by default "text/plain".
Gitweb guesses mimetype of a file to display based on extension
- of its filename, using <tt>$mimetypes_file</tt> (if set and file exists)
+ of its filename, using <code>$mimetypes_file</code> (if set and file exists)
and <em>/etc/mime.types</em> files (see <strong>mime.types</strong>(5) manpage; only
filename extension rules are supported by gitweb).
</p>
@@ -1331,7 +1329,7 @@ involve file copies ('-C') or criss-cross renames ('-B').</p></div> </div>
<div class="sect2">
<h3 id="_some_optional_features_and_policies">Some optional features and policies</h3>
-<div class="paragraph"><p>Most of features are configured via <tt>%feature</tt> hash; however some of extra
+<div class="paragraph"><p>Most of features are configured via <code>%feature</code> hash; however some of extra
gitweb features can be turned on and configured using variables described
below. This list beside configuration variables that control how gitweb
looks does contain variables configuring administrative side of gitweb
@@ -1345,17 +1343,17 @@ affects how "summary" pages look like, or load limiting).</p></div> <p>
List of Git base URLs. These URLs are used to generate URLs
describing from where to fetch a project, which are shown on
- project summary page. The full fetch URL is "<tt>$git_base_url/$project</tt>",
+ project summary page. The full fetch URL is "<code>$git_base_url/$project</code>",
for each element of this list. You can set up multiple base URLs
- (for example one for <tt>git://</tt> protocol, and one for <tt>http://</tt>
+ (for example one for <code>git://</code> protocol, and one for <code>http://</code>
protocol).
</p>
<div class="paragraph"><p>Note that per repository configuration can be set in <em>$GIT_DIR/cloneurl</em>
-file, or as values of multi-value <tt>gitweb.url</tt> configuration variable in
+file, or as values of multi-value <code>gitweb.url</code> configuration variable in
project config. Per-repository configuration takes precedence over value
-composed from <tt>@git_base_url_list</tt> elements and project name.</p></div>
+composed from <code>@git_base_url_list</code> elements and project name.</p></div>
<div class="paragraph"><p>You can setup one single value (single entry/item in this list) at build
-time by setting the <tt>GITWEB_BASE_URL</tt> built-time configuration variable.
+time by setting the <code>GITWEB_BASE_URL</code> built-time configuration variable.
By default it is set to (), i.e. an empty list. This means that gitweb
would not try to create project URL (to fetch) from project name.</p></div>
</dd>
@@ -1366,7 +1364,7 @@ $projects_list_group_categories <p>
Whether to enables the grouping of projects by category on the project
list page. The category of a project is determined by the
- <tt>$GIT_DIR/category</tt> file or the <tt>gitweb.category</tt> variable in each
+ <code>$GIT_DIR/category</code> file or the <code>gitweb.category</code> variable in each
repository’s configuration. Disabled by default (set to 0).
</p>
</dd>
@@ -1378,7 +1376,7 @@ $project_list_default_category Default category for projects for which none is specified. If this is
set to the empty string, such projects will remain uncategorized and
listed at the top, above categorized projects. Used only if project
- categories are enabled, which means if <tt>$projects_list_group_categories</tt>
+ categories are enabled, which means if <code>$projects_list_group_categories</code>
is true. By default set to "" (empty string).
</p>
</dd>
@@ -1406,7 +1404,7 @@ $maxload tasks on the system — processes that are actually running — averaged
over the last minute.
</p>
-<div class="paragraph"><p>Set <tt>$maxload</tt> to undefined value (<tt>undef</tt>) to turn this feature off.
+<div class="paragraph"><p>Set <code>$maxload</code> to undefined value (<code>undef</code>) to turn this feature off.
The default value is 300.</p></div>
</dd>
<dt class="hdlist1">
@@ -1438,15 +1436,15 @@ $per_request_config </p>
<div class="listingblock">
<div class="content">
-<pre><tt>our $per_request_config = sub {
+<pre><code>our $per_request_config = sub {
$ENV{GL_USER} = $cgi->remote_user || "gitweb";
-};</tt></pre>
+};</code></pre>
</div></div>
-<div class="paragraph"><p>If <tt>$per_request_config</tt> is not a code reference, it is interpreted as boolean
+<div class="paragraph"><p>If <code>$per_request_config</code> is not a code reference, it is interpreted as boolean
value. If it is true gitweb will process config files once per request,
and if it is false gitweb will process config files only once, each time it
is executed. True by default (set to 1).</p></div>
-<div class="paragraph"><p><strong>NOTE</strong>: <tt>$my_url</tt>, <tt>$my_uri</tt>, and <tt>$base_url</tt> are overwritten with their default
+<div class="paragraph"><p><strong>NOTE</strong>: <code>$my_url</code>, <code>$my_uri</code>, and <code>$base_url</code> are overwritten with their default
values before every request, so if you want to change them, be sure to set
this variable to true or a code reference effecting the desired changes.</p></div>
<div class="paragraph"><p>This variable matters only when using persistent web environments that
@@ -1472,7 +1470,7 @@ $version </p>
<div class="listingblock">
<div class="content">
-<pre><tt>our $version .= " with caching";</tt></pre>
+<pre><code>our $version .= " with caching";</code></pre>
</div></div>
<div class="paragraph"><p>if you run modified version of gitweb with caching support. This variable
is purely informational, used e.g. in the "generator" meta header in HTML
@@ -1489,7 +1487,7 @@ $my_uri Full URL and absolute URL of the gitweb script;
in earlier versions of gitweb you might have need to set those
variables, but now there should be no need to do it. See
- <tt>$per_request_config</tt> if you need to set them still.
+ <code>$per_request_config</code> if you need to set them still.
</p>
</dd>
<dt class="hdlist1">
@@ -1498,11 +1496,11 @@ $base_url <dd>
<p>
Base URL for relative URLs in pages generated by gitweb,
- (e.g. <tt>$logo</tt>, <tt>$favicon</tt>, <tt>@stylesheets</tt> if they are relative URLs),
+ (e.g. <code>$logo</code>, <code>$favicon</code>, <code>@stylesheets</code> if they are relative URLs),
needed and used <em><base href="$base_url"></em> only for URLs with nonempty
PATH_INFO. Usually gitweb sets its value correctly,
and there is no need to set this variable, e.g. to $my_uri or "/".
- See <tt>$per_request_config</tt> if you need to override it anyway.
+ See <code>$per_request_config</code> if you need to override it anyway.
</p>
</dd>
</dl></div>
@@ -1513,26 +1511,26 @@ $base_url <h2 id="_configuring_gitweb_features">CONFIGURING GITWEB FEATURES</h2>
<div class="sectionbody">
<div class="paragraph"><p>Many gitweb features can be enabled (or disabled) and configured using the
-<tt>%feature</tt> hash. Names of gitweb features are keys of this hash.</p></div>
-<div class="paragraph"><p>Each <tt>%feature</tt> hash element is a hash reference and has the following
+<code>%feature</code> hash. Names of gitweb features are keys of this hash.</p></div>
+<div class="paragraph"><p>Each <code>%feature</code> hash element is a hash reference and has the following
structure:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>"<feature_name>" => {
+<pre><code>"<feature_name>" => {
"sub" => <feature-sub (subroutine)>,
"override" => <allow-override (boolean)>,
"default" => [ <options>... ]
-},</tt></pre>
+},</code></pre>
</div></div>
<div class="paragraph"><p>Some features cannot be overridden per project. For those
-features the structure of appropriate <tt>%feature</tt> hash element has a simpler
+features the structure of appropriate <code>%feature</code> hash element has a simpler
form:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>"<feature_name>" => {
+<pre><code>"<feature_name>" => {
"override" => 0,
"default" => [ <options>... ]
-},</tt></pre>
+},</code></pre>
</div></div>
<div class="paragraph"><p>As one can see it lacks the 'sub' element.</p></div>
<div class="paragraph"><p>The meaning of each part of feature configuration is described
@@ -1549,11 +1547,11 @@ default <div class="paragraph"><p>Note that it is currently <strong>always</strong> an array reference, even if
feature doesn’t accept any configuration parameters, and 'default'
is used only to turn it on or off. In such case you turn feature on
-by setting this element to <tt>[1]</tt>, and torn it off by setting it to
-<tt>[0]</tt>. See also the passage about the "blame" feature in the "Examples"
+by setting this element to <code>[1]</code>, and torn it off by setting it to
+<code>[0]</code>. See also the passage about the "blame" feature in the "Examples"
section.</p></div>
<div class="paragraph"><p>To disable features that accept parameters (are configurable), you
-need to set this element to empty list i.e. <tt>[]</tt>.</p></div>
+need to set this element to empty list i.e. <code>[]</code>.</p></div>
</dd>
<dt class="hdlist1">
override
@@ -1564,7 +1562,7 @@ override overridable, which means that it can be configured
(or enabled/disabled) on a per-repository basis.
</p>
-<div class="paragraph"><p>Usually given "<feature>" is configurable via the <tt>gitweb.<feature></tt>
+<div class="paragraph"><p>Usually given "<feature>" is configurable via the <code>gitweb.<feature></code>
config variable in the per-repository Git configuration file.</p></div>
<div class="paragraph"><p><strong>Note</strong> that no feature is overridable by default.</p></div>
</dd>
@@ -1581,8 +1579,8 @@ sub </dd>
</dl></div>
<div class="sect2">
-<h3 id="_features_in_tt_feature_tt">Features in <tt>%feature</tt></h3>
-<div class="paragraph"><p>The gitweb features that are configurable via <tt>%feature</tt> hash are listed
+<h3 id="_features_in_code_feature_code">Features in <code>%feature</code></h3>
+<div class="paragraph"><p>The gitweb features that are configurable via <code>%feature</code> hash are listed
below. This should be a complete list, but ultimately the authoritative
and complete list is in gitweb.cgi source code, with features described
in the comments.</p></div>
@@ -1597,7 +1595,7 @@ blame This can be very CPU-intensive and is therefore disabled by default.
</p>
<div class="paragraph"><p>This feature can be configured on a per-repository basis via
-repository’s <tt>gitweb.blame</tt> configuration variable (boolean).</p></div>
+repository’s <code>gitweb.blame</code> configuration variable (boolean).</p></div>
</dd>
<dt class="hdlist1">
snapshot
@@ -1610,12 +1608,12 @@ snapshot This can potentially generate high traffic if you have large project.
</p>
<div class="paragraph"><p>The value of 'default' is a list of names of snapshot formats,
-defined in <tt>%known_snapshot_formats</tt> hash, that you wish to offer.
+defined in <code>%known_snapshot_formats</code> hash, that you wish to offer.
Supported formats include "tgz", "tbz2", "txz" (gzip/bzip2/xz
compressed tar archive) and "zip"; please consult gitweb sources for
a definitive list. By default only "tgz" is offered.</p></div>
<div class="paragraph"><p>This feature can be configured on a per-repository basis via
-repository’s <tt>gitweb.blame</tt> configuration variable, which contains
+repository’s <code>gitweb.blame</code> configuration variable, which contains
a comma separated list of formats or "none" to disable snapshots.
Unknown values are ignored.</p></div>
</dd>
@@ -1629,7 +1627,7 @@ grep This can be potentially CPU-intensive, of course. Enabled by default.
</p>
<div class="paragraph"><p>This feature can be configured on a per-repository basis via
-repository’s <tt>gitweb.grep</tt> configuration variable (boolean).</p></div>
+repository’s <code>gitweb.grep</code> configuration variable (boolean).</p></div>
</dd>
<dt class="hdlist1">
pickaxe
@@ -1642,10 +1640,10 @@ pickaxe still potentially CPU-intensive. Enabled by default.
</p>
<div class="paragraph"><p>The pickaxe search is described in <a href="git-log.html">git-log(1)</a> (the
-description of <tt>-S<string></tt> option, which refers to pickaxe entry in
+description of <code>-S<string></code> option, which refers to pickaxe entry in
<a href="gitdiffcore.html">gitdiffcore(7)</a> for more details).</p></div>
<div class="paragraph"><p>This feature can be configured on a per-repository basis by setting
-repository’s <tt>gitweb.pickaxe</tt> configuration variable (boolean).</p></div>
+repository’s <code>gitweb.pickaxe</code> configuration variable (boolean).</p></div>
</dd>
<dt class="hdlist1">
show-sizes
@@ -1653,12 +1651,12 @@ show-sizes <dd>
<p>
Enable showing size of blobs (ordinary files) in a "tree" view, in a
- separate column, similar to what <tt>ls -l</tt> does; see description of
- <tt>-l</tt> option in <a href="git-ls-tree.html">git-ls-tree(1)</a> manpage. This costs a bit of
+ separate column, similar to what <code>ls -l</code> does; see description of
+ <code>-l</code> option in <a href="git-ls-tree.html">git-ls-tree(1)</a> manpage. This costs a bit of
I/O. Enabled by default.
</p>
<div class="paragraph"><p>This feature can be configured on a per-repository basis via
-repository’s <tt>gitweb.showsizes</tt> configuration variable (boolean).</p></div>
+repository’s <code>gitweb.showsizes</code> configuration variable (boolean).</p></div>
</dd>
<dt class="hdlist1">
patches
@@ -1674,7 +1672,7 @@ patches Default value is 16.
</p>
<div class="paragraph"><p>This feature can be configured on a per-repository basis via
-repository’s <tt>gitweb.patches</tt> configuration variable (integer).</p></div>
+repository’s <code>gitweb.patches</code> configuration variable (integer).</p></div>
</dd>
<dt class="hdlist1">
avatar
@@ -1691,12 +1689,12 @@ If an unknown provider is specified, the feature is disabled. <strong>Note</strong> that some providers might require extra Perl packages to be
installed; see <em>gitweb/INSTALL</em> for more details.</p></div>
<div class="paragraph"><p>This feature can be configured on a per-repository basis via
-repository’s <tt>gitweb.avatar</tt> configuration variable.</p></div>
-<div class="paragraph"><p>See also <tt>%avatar_size</tt> with pixel sizes for icons and avatars
+repository’s <code>gitweb.avatar</code> configuration variable.</p></div>
+<div class="paragraph"><p>See also <code>%avatar_size</code> with pixel sizes for icons and avatars
("default" is used for one-line like "log" and "shortlog", "double"
is used for two-line like "commit", "commitdiff" or "tag"). If the
default font sizes or lineheights are changed (e.g. via adding extra
-CSS stylesheet in <tt>@stylesheets</tt>), it may be appropriate to change
+CSS stylesheet in <code>@stylesheets</code>), it may be appropriate to change
these values.</p></div>
</dd>
<dt class="hdlist1">
@@ -1705,12 +1703,12 @@ highlight <dd>
<p>
Server-side syntax highlight support in "blob" view. It requires
- <tt>$highlight_bin</tt> program to be available (see the description of
+ <code>$highlight_bin</code> program to be available (see the description of
this variable in the "Configuration variables" section above),
and therefore is disabled by default.
</p>
<div class="paragraph"><p>This feature can be configured on a per-repository basis via
-repository’s <tt>gitweb.highlight</tt> configuration variable (boolean).</p></div>
+repository’s <code>gitweb.highlight</code> configuration variable (boolean).</p></div>
</dd>
<dt class="hdlist1">
remote_heads
@@ -1724,7 +1722,7 @@ remote_heads to browse local repositories, enables and uses this feature.
</p>
<div class="paragraph"><p>This feature can be configured on a per-repository basis via
-repository’s <tt>gitweb.remote_heads</tt> configuration variable (boolean).</p></div>
+repository’s <code>gitweb.remote_heads</code> configuration variable (boolean).</p></div>
</dd>
</dl></div>
<div class="paragraph"><p>The remaining features cannot be overridden on a per project basis.</p></div>
@@ -1736,7 +1734,7 @@ search <p>
Enable text search, which will list the commits which match author,
committer or commit text to a given string; see the description of
- <tt>--author</tt>, <tt>--committer</tt> and <tt>--grep</tt> options in <a href="git-log.html">git-log(1)</a>
+ <code>--author</code>, <code>--committer</code> and <code>--grep</code> options in <a href="git-log.html">git-log(1)</a>
manpage. Enabled by default.
</p>
<div class="paragraph"><p>Project specific override is not supported.</p></div>
@@ -1748,14 +1746,14 @@ forks <p>
If this feature is enabled, gitweb considers projects in
subdirectories of project root (basename) to be forks of existing
- projects. For each project <tt>$projname.git</tt>, projects in the
- <tt>$projname/</tt> directory and its subdirectories will not be
+ projects. For each project <code>$projname.git</code>, projects in the
+ <code>$projname/</code> directory and its subdirectories will not be
shown in the main projects list. Instead, a '+' mark is shown
- next to <tt>$projname</tt>, which links to a "forks" view that lists all
- the forks (all projects in <tt>$projname/</tt> subdirectory). Additionally
+ next to <code>$projname</code>, which links to a "forks" view that lists all
+ the forks (all projects in <code>$projname/</code> subdirectory). Additionally
a "forks" view for a project is linked from project summary page.
</p>
-<div class="paragraph"><p>If the project list is taken from a file (<tt>$projects_list</tt> points to a
+<div class="paragraph"><p>If the project list is taken from a file (<code>$projects_list</code> points to a
file), forks are only recognized if they are listed after the main project
in that file.</p></div>
<div class="paragraph"><p>Project specific override is not supported.</p></div>
@@ -1770,9 +1768,9 @@ actions </p>
<div class="paragraph"><p>The "default" value consists of a list of triplets in the form
‘("<label>", "<link>", "<position>")` where "position" is the label
-after which to insert the link, "link" is a format string where <tt>%n</tt>
-expands to the project name, <tt>%f</tt> to the project path within the
-filesystem (i.e. "$projectroot/$project"), <tt>%h</tt> to the current hash
+after which to insert the link, "link" is a format string where <code>%n</code>
+expands to the project name, <code>%f</code> to the project path within the
+filesystem (i.e. "$projectroot/$project"), <code>%h</code> to the current hash
('h’ gitweb parameter) and ‘%b` to the current hash base
('hb’ gitweb parameter); ‘%%` expands to '%’.</p></div>
<div class="paragraph"><p>For example, at the time this page was written, the <a href="http://repo.or.cz">http://repo.or.cz</a>
@@ -1780,11 +1778,11 @@ Git hosting site set it to the following to enable graphical log (using the third party tool <strong>git-browser</strong>):</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>$feature{'actions'}{'default'} =
- [ ('graphiclog', '/git-browser/by-commit.html?r=%n', 'summary')];</tt></pre>
+<pre><code>$feature{'actions'}{'default'} =
+ [ ('graphiclog', '/git-browser/by-commit.html?r=%n', 'summary')];</code></pre>
</div></div>
<div class="paragraph"><p>This adds a link titled "graphiclog" after the "summary" link, leading to
-<tt>git-browser</tt> script, passing <tt>r=<project></tt> as a query parameter.</p></div>
+<code>git-browser</code> script, passing <code>r=<project></code> as a query parameter.</p></div>
<div class="paragraph"><p>Project specific override is not supported.</p></div>
</dd>
<dt class="hdlist1">
@@ -1813,12 +1811,12 @@ javascript-timezone hasn’t selected some other time zone and saved it in a cookie), a name of cookie
where to store selected time zone, and a CSS class used to mark up
dates for manipulation. If you want to turn this feature off, set "default"
-to empty list: <tt>[]</tt>.</p></div>
+to empty list: <code>[]</code>.</p></div>
<div class="paragraph"><p>Typical gitweb config files will only change starting (default) time zone,
and leave other elements at their default values:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>$feature{'javascript-timezone'}{'default'}[0] = "utc";</tt></pre>
+<pre><code>$feature{'javascript-timezone'}{'default'}[0] = "utc";</code></pre>
</div></div>
<div class="paragraph"><p>The example configuration presented here is guaranteed to be backwards
and forward compatible.</p></div>
@@ -1842,26 +1840,26 @@ extra-branch-refs </p>
<div class="listingblock">
<div class="content">
-<pre><tt>$feature{'extra-branch-refs'}{'default'} =
- ['sandbox', 'wip', 'other'];</tt></pre>
+<pre><code>$feature{'extra-branch-refs'}{'default'} =
+ ['sandbox', 'wip', 'other'];</code></pre>
</div></div>
<div class="paragraph"><p>This feature can be configured on per-repository basis after setting
$feature{<em>extra-branch-refs</em>}{<em>override</em>} to true, via repository’s
-<tt>gitweb.extraBranchRefs</tt> configuration variable, which contains a
+<code>gitweb.extraBranchRefs</code> configuration variable, which contains a
space separated list of refs. An example:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>[gitweb]
- extraBranchRefs = sandbox wip other</tt></pre>
+<pre><code>[gitweb]
+ extraBranchRefs = sandbox wip other</code></pre>
</div></div>
<div class="paragraph"><p>The gitweb.extraBranchRefs is actually a multi-valued configuration
variable, so following example is also correct and the result is the
same as of the snippet above:</p></div>
<div class="listingblock">
<div class="content">
-<pre><tt>[gitweb]
+<pre><code>[gitweb]
extraBranchRefs = sandbox
- extraBranchRefs = wip other</tt></pre>
+ extraBranchRefs = wip other</code></pre>
</div></div>
<div class="paragraph"><p>It is an error to specify a ref that does not pass "git check-ref-format"
scrutiny. Duplicated values are filtered.</p></div>
@@ -1878,18 +1876,18 @@ scrutiny. Duplicated values are filtered.</p></div> the following in your GITWEB_CONFIG file:</p></div>
<div class="literalblock">
<div class="content">
-<pre><tt>$feature{'blame'}{'default'} = [1];
-$feature{'blame'}{'override'} = 1;</tt></pre>
+<pre><code>$feature{'blame'}{'default'} = [1];
+$feature{'blame'}{'override'} = 1;</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
-<pre><tt>$feature{'pickaxe'}{'default'} = [1];
-$feature{'pickaxe'}{'override'} = 1;</tt></pre>
+<pre><code>$feature{'pickaxe'}{'default'} = [1];
+$feature{'pickaxe'}{'override'} = 1;</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
-<pre><tt>$feature{'snapshot'}{'default'} = ['zip', 'tgz'];
-$feature{'snapshot'}{'override'} = 1;</tt></pre>
+<pre><code>$feature{'snapshot'}{'default'} = ['zip', 'tgz'];
+$feature{'snapshot'}{'override'} = 1;</code></pre>
</div></div>
<div class="paragraph"><p>If you allow overriding for the snapshot feature, you can specify which
snapshot formats are globally disabled. You can also add any command-line
@@ -1898,8 +1896,8 @@ can disable Zip compressed snapshots and set <strong>gzip</strong>(1) to run at adding the following lines to your gitweb configuration file:</p></div>
<div class="literalblock">
<div class="content">
-<pre><tt>$known_snapshot_formats{'zip'}{'disabled'} = 1;
-$known_snapshot_formats{'tgz'}{'compressor'} = ['gzip','-6'];</tt></pre>
+<pre><code>$known_snapshot_formats{'zip'}{'disabled'} = 1;
+$known_snapshot_formats{'tgz'}{'compressor'} = ['gzip','-6'];</code></pre>
</div></div>
</div>
</div>
@@ -1907,7 +1905,7 @@ $known_snapshot_formats{'tgz'}{'compressor'} = ['gzip','-6'];</tt></pre> <h2 id="_bugs">BUGS</h2>
<div class="sectionbody">
<div class="paragraph"><p>Debugging would be easier if the fallback configuration file
-(<tt>/etc/gitweb.conf</tt>) and environment variable to override its location
+(<code>/etc/gitweb.conf</code>) and environment variable to override its location
(<em>GITWEB_CONFIG_SYSTEM</em>) had names reflecting their "fallback" role.
The current names are kept to avoid breaking working setups.</p></div>
</div>
|