"Fossies" - the Fresh Open Source Software Archive

Member "viewvc-1.2.1/conf/viewvc.conf.dist" (26 Mar 2020, 47270 Bytes) of package /linux/misc/viewvc-1.2.1.tar.gz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. See also the latest Fossies "Diffs" side-by-side code changes report for "viewvc.conf.dist": 1.1.28_vs_1.2.1.

    1 ##---------------------------------------------------------------------------
    2 ##
    3 ## Configuration file for ViewVC
    4 ##
    5 ## Information on ViewVC is located at the following web site:
    6 ##     http://viewvc.org/
    7 ##
    8 ##---------------------------------------------------------------------------
    9 
   10 ## THE FORMAT OF THIS CONFIGURATION FILE
   11 ##
   12 ##    This file is delineated by sections, specified in [brackets].  Within 
   13 ##    each section, are a number of configuration settings.  These settings
   14 ##    take the form of: name = value.  Values may be continued on the
   15 ##    following line by indenting the continued line.
   16 ##
   17 ##    WARNING:  Indentation *always* means continuation.  Name=value lines
   18 ##    should always start in column zero.
   19 ##
   20 ##    Comments should always start in column zero, and are identified
   21 ##    with "#".  By default each of the configuration items is
   22 ##    commented out, with the default value of the option shown.
   23 ##    You'll need to remove the '#' that precedes configuration
   24 ##    options whose values you wish to modify.
   25 ##
   26 ##    Certain configuration settings may have multiple values.  These should 
   27 ##    be separated by a comma.  The settings where this is allowed are noted 
   28 ##    below.  Any other setting that requires special syntax is noted at that
   29 ##    setting.
   30 ## 
   31 ##
   32 ## SOME TERMINOLOGY USED HEREIN
   33 ##
   34 ##    "root" - This is a CVS or Subversion repository.  For Subversion, the
   35 ##        meaning is pretty clear, as the virtual, versioned directory tree
   36 ##        stored inside a Subversion repository looks nothing like the actual
   37 ##        tree visible with shell utilities that holds the repository.  For
   38 ##        CVS, this is more confusing, because CVS's repository layout mimics
   39 ##        (actually, defines) the layout of the stuff housed in the repository.
   40 ##        But a CVS repository can be identified by the presence of a CVSROOT
   41 ##        subdirectory in its root directory.
   42 ##
   43 ##    "module" - A module is a top-level subdirectory of a root, usually
   44 ##        associated with the concept of a single "project" among many housed
   45 ##        within a single repository.
   46 ##
   47 ##    "context" - Contexts are a concept for grouping together several
   48 ##        repositories, similar to using (sub)directories.  For a root name
   49 ##        containing a slash (/), the context is defined as the part of the
   50 ##        root name before the (last) slash.  A root name without a slash is
   51 ##        said to have an empty or no context.
   52 ##
   53 ##
   54 ## BASIC VIEWVC CONFIGURATION HINTS
   55 ##
   56 ##    While ViewVC has quite a few configuration options, you generally
   57 ##    only need to change a small subset of them to get your ViewVC
   58 ##    installation working properly.  Here are some options that we
   59 ##    recommend you pay attention to.  Of course, don't try to change the
   60 ##    options here -- do so in the relevant section of the configuration
   61 ##    file below.
   62 ##    
   63 ##    For correct operation, you will probably need to change the following
   64 ##    configuration variables:
   65 ##   
   66 ##       cvs_roots (for CVS)
   67 ##       svn_roots (for Subversion)
   68 ##       root_parents (for CVS or Subversion)
   69 ##       default_root
   70 ##       root_as_url_component
   71 ##       rcs_dir
   72 ##       mime_types_files
   73 ##       the many options in the [utilities] section
   74 ##   
   75 ##    It is usually desirable to change the following variables:
   76 ##   
   77 ##       address
   78 ##       forbidden
   79 ##   
   80 ##    To optimize delivery of ViewVC static files:
   81 ##   
   82 ##       docroot
   83 ##   
   84 ##    To customize the display of ViewVC for your site:
   85 ##   
   86 ##       template_dir
   87 ##       the [templates] override section
   88 ##
   89 
   90 ##---------------------------------------------------------------------------
   91 [general]
   92 
   93 ## cvs_roots: Specifies each of the CVS roots on your system and
   94 ## assigns names to them. Each root should be given by a "name: path"
   95 ## value (where the path is an absolute filesystem path). Multiple roots
   96 ## should be separated by commas and can be placed on separate lines.
   97 ##
   98 ## Example:
   99 ## cvs_roots = cvsroot: /opt/cvs/repos1,
  100 ##             anotherroot: /usr/local/cvs/repos2,
  101 ##             somecontext/root: /usr/local/cvs/repos3
  102 ##
  103 #cvs_roots =
  104 
  105 ## svn_roots: Specifies each of the Subversion roots (repositories) on
  106 ## your system and assigns names to them. Each root should be given by
  107 ## a "name: path" value (where the path is an absolute filesystem path).
  108 ## Multiple roots should be separated by commas and can be placed on
  109 ## separate lines.
  110 ##
  111 ## NOTE: ViewVC offers *experimental* support for displaying remote
  112 ## Subversion repositories.  Simply use the repository's URL instead
  113 ## of a local filesystem path when defining the root.
  114 ##
  115 ## Example:
  116 ## svn_roots = svnrepos: /opt/svn/,
  117 ##             anotherrepos: /usr/local/svn/repos2,
  118 ##             somecontext/repos: /usr/local/svn/repos3
  119 ##
  120 #svn_roots =
  121 
  122 ## root_parents: Specifies a list of directories under which any
  123 ## number of repositories may reside.  You can specify multiple root
  124 ## parents separated by commas or new lines, each of which is of the
  125 ## form "path [= context] : type" (where the type is either "cvs" or
  126 ## "svn", the path is an absolute filesystem path, and the (optional)
  127 ## context is prepended to each repository's name to determine the
  128 ## final root name).
  129 ##
  130 ## Rather than force you to add a new entry to 'cvs_roots' or
  131 ## 'svn_roots' each time you create a new repository, ViewVC rewards
  132 ## you for organizing all your repositories under a few parent
  133 ## directories by allowing you to simply tell it about those parent
  134 ## directories.  ViewVC will then notice each repository of the
  135 ## specified type in that directory as a root whose name is the
  136 ## subdirectory in which that repository lives.
  137 ##
  138 ## For example, if you have three Subversion repositories located at
  139 ## /opt/svn/projects, /opt/svn/websites, and /opt/svn/devstuff, you
  140 ## could list them individually in svn_roots like so:
  141 ##
  142 ##    svn_roots = projects: /opt/svn/projects,
  143 ##                websites: /opt/svn/websites,
  144 ##                devstuff: /opt/svn/devstuff
  145 ##
  146 ## or you could instead use the root_parents configuration option:
  147 ##
  148 ##    root_parents = /opt/svn: svn
  149 ##
  150 ## The benefit of this latter approach is that, as you add new
  151 ## repositories to your /opt/svn directory, they automatically become
  152 ## available for display in ViewVC without additional configuration.
  153 ##
  154 ## WARNING: the root names derived for repositories configured via the
  155 ## root_parents option can, of course, clash with names you have
  156 ## defined in your cvs_roots or svn_roots configuration items.  If
  157 ## this occurs, you can either rename the offending repository on
  158 ## disk, grant new names to the clashing item in cvs_roots or
  159 ## svn_roots, or use different contexts.  Each parent path is processed
  160 ## sequentially, so the names of repositories under later parent paths
  161 ## may override earlier ones.
  162 ##
  163 ## Example:
  164 ## root_parents = /opt/svn: svn,
  165 ##                /home/alice/svn = alice : svn,
  166 ##                /home/bob/svn = bob : svn,
  167 ##                /opt/cvs: cvs
  168 ##
  169 #root_parents =
  170 
  171 ## renamed_roots: Specifies a mapping between the old names of version control
  172 ## roots/repositories and their current names.
  173 ##
  174 ## When the name of a CVS or Subversion root has been changed (e.g. the project
  175 ## name has been changed), existing external links to views of that root will
  176 ## cease to resolve.  This mapping causes ViewVC to continue to recognize the
  177 ## previous root name and automatically redirect the web browser to the appropriate
  178 ## location in the renamed root.
  179 ##
  180 ## Example:
  181 ## renamed_roots = old_root_name: new_root_name,
  182 ##                 backrub: google,
  183 ##                 context1/root1: context2/root2
  184 #renamed_roots = 
  185 
  186 ## default_root: This is the name of the default root.  Valid names
  187 ## include those explicitly listed in the cvs_roots and svn_roots
  188 ## configuration options, as well as those implicitly indicated by
  189 ## virtue of being the basenames of repositories found in the
  190 ## root_parents option locations.
  191 ##
  192 ## NOTE: This setting is ignored when root_as_url_component is enabled.
  193 ##
  194 ## Example:
  195 ## default_root = cvsroot
  196 ##
  197 #default_root =
  198 
  199 ## mime_types_files: This is a list of pathnames to a set of MIME type
  200 ## mapping files to help ViewVC guess the correct MIME type of a
  201 ## versioned file.  The pathnames listed here are specified in order of
  202 ## authoritativeness either as absolute paths or relative to this
  203 ## configuration file.
  204 ##
  205 ## As a convenience, ViewVC provides a MIME type mapping file
  206 ## (mimetypes.conf) which is, by default, the preferred provider of
  207 ## MIME type mapping answers, but which is also empty.  If you find
  208 ## that ViewVC is unable to accurately guess MIME types based on the
  209 ## extensions of some of your versioned files, you can add records of
  210 ## your preferred mappings to the provided mimetypes.conf file (or to
  211 ## your system's mapping files, if you wish).
  212 ##
  213 ## You might, for example, wish to have ViewVC also consult the mapping
  214 ## files provided by your operating system and Apache.
  215 ##
  216 ## Example:
  217 ## mime_types_files = mimetypes.conf,
  218 ##                    /etc/mime.types,
  219 ##                    /usr/local/apache2/conf/mime.types
  220 ##
  221 #mime_types_files = mimetypes.conf
  222 
  223 ## address: The address of the local repository maintainer.  (This
  224 ## option is provided only as a convenience for ViewVC installations
  225 ## which are using the default template set, where the value of this
  226 ## option will be displayed in the footer of every ViewVC page.)
  227 ##
  228 ## Example:
  229 ## address = admin@server.com
  230 ##
  231 #address =
  232 
  233 ## kv_files: Provides a mechanism for custom key/value pairs to be
  234 ## available to templates.  These are stored in key/value (KV) files.
  235 ##
  236 ## The paths of the KV files are listed here, specified either as
  237 ## absolute paths or relative to this configuration file.  The files
  238 ## use the same format as this configuration file, containing one or
  239 ## more user-defined sections, and user-defined options in those
  240 ## sections.  ViewVC makes these options available to template authors
  241 ## as:
  242 ##
  243 ##    kv.SECTION.OPTION
  244 ##
  245 ## Note that an option name can be dotted.  For example:
  246 ##
  247 ##    [my_images]
  248 ##    logos.small = /images/small-logo.png
  249 ##    logos.big = /images/big-logo.png
  250 ##
  251 ## Templates can use these with a directive like:  [kv.my_images.logos.small]
  252 ##
  253 ## Note that section names which are common to multiple KV files will
  254 ## be merged.  If two files have a [my_images] section, then the
  255 ## options in those two like-named sections will be merged together.
  256 ## If two files have the same option name in a section, then one will
  257 ## overwrite the other (and which one "wins" is unspecified).
  258 ##
  259 ## To further categorize the KV files, and how the values are provided to
  260 ## the templates, a KV file name may be annotated with an additional level
  261 ## of dotted naming. For example:
  262 ##
  263 ##    kv_files = [asf]kv/images.conf
  264 ##
  265 ## Assuming the same section as above, the template would refer to an image
  266 ## using [kv.asf.my_images.logos.small]
  267 ##
  268 ## Lastly, it is possible to use %lang% in the filenames to specify a
  269 ## substitution of the selected language-tag.
  270 ##
  271 ## Example:
  272 ## kv_files = kv/file1.conf, kv/file2.conf, [i18n]kv/%lang%_data.conf
  273 ##
  274 #kv_files =
  275 
  276 ## This option is a comma-separated list of language-tag values
  277 ## available to ViewVC.  The first language-tag listed is the default
  278 ## language, and will be used if an Accept-Language header is not
  279 ## present in the request, or none of the user's requested languages
  280 ## are available.  If there are ties on the selection of a language,
  281 ## then the first to appear in the list is chosen.
  282 ##
  283 ## Example:
  284 ## languages = en-us, en-gb, de
  285 ##
  286 #languages = en-us
  287 
  288 
  289 ##---------------------------------------------------------------------------
  290 [utilities]
  291 
  292 ## ViewVC uses (sometimes optionally) various third-party programs to do some
  293 ## of the heavy lifting.  Generally, it will attempt to execute those utility
  294 ## programs in such a way that if they are found in ViewVC's executable
  295 ## search path ($PATH, %PATH%, etc.) all is well.  But sometimes these tools
  296 ## aren't installed in the executable search path, so here's where you can
  297 ## tell ViewVC where to find them.
  298 ##
  299 ## NOTE: Options with a "_dir" suffix are for configuring the
  300 ## directories in which certain programs live.  Note that this might
  301 ## not be the same directory into which the program's installer dumped
  302 ## the whole program package -- we want the deepest directory in which
  303 ## the executable program itself resides ("C:\rcstools\bin\win32"
  304 ## rather than just "C:\rcstools", for example).  The values of options
  305 ## whose names lack the "_dir" suffix should point to the actual
  306 ## program itself (such as "C:\Program Files\cvsnt\cvs.exe").
  307 
  308 
  309 ## rcs_dir: Directory in which the RCS utilities are installed, used
  310 ## for viewing CVS repositories.
  311 ##
  312 ## Example:
  313 ## rcs_dir = /usr/bin/
  314 ##
  315 #rcs_dir =
  316 
  317 ## cvsnt: Location of cvsnt program.  ViewVC can use CVSNT (www.cvsnt.org)
  318 ## instead of the RCS utilities to retrieve information from CVS
  319 ## repositories.  To enable use of CVSNT, set the "cvsnt" value to the
  320 ## path of the CVSNT executable. (If CVSNT is on the standard path, you
  321 ## can also set it to the name of the CVSNT executable). By default
  322 ## "cvsnt" is set to "cvs" on Windows and is not set on other platforms.
  323 ##
  324 ## Examples:
  325 ## cvsnt = K:\Program Files\cvsnt\cvs.exe
  326 ## cvsnt = /usr/bin/cvs
  327 ## cvsnt = cvs
  328 ##
  329 #cvsnt =
  330 
  331 ## diff: Location of the GNU diff program, used for showing file
  332 ## version differences.
  333 ##
  334 ## Example:
  335 ## diff = /usr/bin/diff
  336 ##
  337 #diff = 
  338 
  339 ## cvsgraph: Location of the CvsGraph program, a graphical CVS version
  340 ## graph generator (see options.use_cvsgraph).
  341 ##
  342 ## Example:
  343 ## cvsgraph = /usr/local/bin/cvsgraph
  344 ##
  345 #cvsgraph =
  346 
  347 
  348 ##---------------------------------------------------------------------------
  349 [options]
  350 
  351 ## root_as_url_component: Interpret the first path component in the URL
  352 ## after the script location as the root to use.  This is an
  353 ## alternative to using the "root=" query key. If ViewVC is configured
  354 ## with multiple repositories, this results in more natural looking
  355 ## ViewVC URLs.
  356 ##
  357 ## NOTE: Enabling this option will break backwards compatibility with
  358 ## any old ViewCVS URL which doesn't have an explicit "root" parameter.
  359 ##
  360 #root_as_url_component = 1
  361 
  362 ## checkout_magic: Use checkout links with magic /*checkout*/ prefixes so
  363 ## checked out HTML pages can have working links to other repository files
  364 ##
  365 ## NOTE: This option is DEPRECATED and should not be used in new ViewVC
  366 ## installations. Setting "default_file_view = co" achieves the same effect
  367 ##
  368 #checkout_magic = 0
  369 
  370 ## allowed_views: List the ViewVC views which are enabled.  Views not
  371 ## in this comma-delited list will not be served (or, will return an
  372 ## error on attempted access).
  373 ##
  374 ## Valid items for this list include: "annotate", "co", "diff", "markup",
  375 ## "roots", "tar".
  376 ##
  377 ## ----------+---------------------------------------------------------
  378 ##    VIEW   |                       DESCRIPTION
  379 ## ----------+---------------------------------------------------------
  380 ##  annotate | The 'annotate' view shows the contents of a single
  381 ##           | revision of a versioned file in exactly the same way as
  382 ##           | the markup view, but with additional line-by-line
  383 ##           | change attribution (the revision number, author, etc.
  384 ##           | the most recent edit to that line of text as of the
  385 ##           | displayed version).
  386 ## ----------+---------------------------------------------------------
  387 ##  co       | The 'co' (aka "checkout" or "download") view isn't
  388 ##           | really a branded view at all, but allows for direct
  389 ##           | downloading of the contents of a single revision of a 
  390 ##           | versioned file.
  391 ## ----------+---------------------------------------------------------
  392 ##  diff     | The 'diff' view displays line-based differences between
  393 ##           | two revisions of a versioned file in a variety of
  394 ##           | different user-selectable formats.
  395 ## ----------+---------------------------------------------------------
  396 ##  markup   | The 'markup' view shows the contents of a single
  397 ##           | revision of a versioned file, with syntax highlighting
  398 ##           | where possible and enabled.  It can also optionally
  399 ##           | show change log information for that revision of the
  400 ##           | file.
  401 ## ----------+---------------------------------------------------------
  402 ##  roots    | The 'roots' view is a simple listing of the various
  403 ##           | repositories which ViewVC has been configured to serve
  404 ##           | to users.
  405 ## ----------+---------------------------------------------------------
  406 ##  tar      | The 'tar' view isn't a branded view, but generates
  407 ##           | a GNU Tar archive file containing a single versioned
  408 ##           | directory and its contents (recursively).
  409 ## ----------+---------------------------------------------------------
  410 ##
  411 #allowed_views = annotate, diff, markup, roots
  412 
  413 ## binary_mime_types: Comma-delimited list of MIME content types (with
  414 ## support for fnmatch- style glob characters) which are considered
  415 ## not-human-readable and for which ViewVC will neither generate links
  416 ## to, nor support the direct display of, non-checkout views which
  417 ## carry the file's content (the 'markup', 'annotate', 'diff', and
  418 ## 'patch' views).
  419 ##
  420 ## NOTE: Handling of this option is given priority over ViewVC's
  421 ## longstanding support for showing web-friendly file formats -- even
  422 ## binary ones such as "image/jpeg" and "image/gif" -- in the 'markup'
  423 ## view.  Thus, if you add "image/*" to this list, 'markup'-view
  424 ## display of JPEG, GIF, and PNG images will be disabled.
  425 ##
  426 ## Example:
  427 ## binary_mime_types = application/octet-stream, image/*, application/pdf, 
  428 ##                     application/vnd*, application/msword, audio/*
  429 ##
  430 #binary_mime_types =
  431 
  432 ## dir_ignored_files: Comma-delimited list of file names or extensions
  433 ## to be ignored within directory view.
  434 ##
  435 ## Example:
  436 ## dir_ignored_files = file1, image.jpg, *.doc, documents.*
  437 ##
  438 #dir_ignored_files = 
  439 
  440 ## authorizer: The name of the ViewVC authorizer plugin to use when
  441 ## authorizing access to repository contents.  This value must be the
  442 ## name of a Python module addressable as vcauth.MODULENAME (most
  443 ## easily accomplished by placing it in ViewVC's lib/vcauth/ directory)
  444 ## and which implements a ViewVCAuthorizer class (as a subclass of
  445 ## vcauth.GenericViewVCAuthorizer).  You can provide custom parameters
  446 ## to the authorizer module by defining configuration sections named
  447 ## "authz-MODULENAME" and adding the parameter keys and values there.
  448 ##
  449 ## ViewVC provides the following modules:
  450 ##   svnauthz    - based on Subversion authz files
  451 ##   forbidden   - simple path glob matches against top-level root directories
  452 ##   forbiddenre - root and path matches against regular expressions
  453 ##
  454 ## NOTE: Only one authorizer may be in use for a given ViewVC request.
  455 ## It doesn't matter if you configure the parameters of multiple
  456 ## authorizer plugins -- only the authorizer whose name is configured
  457 ## here (or effectively configured here via per-vhost or per-root
  458 ## configuration) will be activated.
  459 ##
  460 #authorizer =
  461 
  462 ## hide_cvsroot: Don't show the CVSROOT directory
  463 ##   1      Hide CVSROOT directory
  464 ##   0      Show CVSROOT directory
  465 ##
  466 ## NOTE: Someday this option may be removed in favor of letting
  467 ## individual authorizer plugin hide the CVSROOT.
  468 ##
  469 #hide_cvsroot = 1
  470 
  471 ## mangle_email_addresses: Mangle email addresses in marked-up output.
  472 ## There are various levels of mangling available:
  473 ##   0 - No mangling; markup un-mangled email addresses as hyperlinks
  474 ##   1 - Obfuscation (using entity encoding); no hyperlinking
  475 ##   2 - Data-dropping address truncation; no hyperlinking
  476 ##
  477 ## NOTE: this will not effect the display of versioned file contents, only
  478 ## addresses that appear in version control metadata (e.g. log messages).
  479 ##
  480 #mangle_email_addresses = 0
  481 
  482 ## custom_log_formatting: Specifies mappings of regular expressions to
  483 ## substitution format strings used to URL-ize strings found in
  484 ## revision log messages.  Multiple mappings (specified as
  485 ## REGEXP:FORMATSTRING) may be defined, separated by commas.
  486 ##
  487 ## NOTE: Due to a limitation of the configuration format, commas may
  488 ## not be used in the regular expression portion of each mapping.
  489 ## Commas "in the raw" may not be used in the format string portion,
  490 ## either, but you can probably use the URI-encoded form of the comma
  491 ## ("%2C") instead with no ill side-effects.  If you must specify a
  492 ## colon character in either the regular expression or the format
  493 ## string, escape it with a preceding backslash ("\:").
  494 ##
  495 ## Example:
  496 ## custom_log_formatting =
  497 ##     artf[0-9]+ : http://example.com/tracker?id=\0,
  498 ##     issue ([0-9]+) : http://example.com/bug?id=\1&opts=full%2csortby=id
  499 ##
  500 #custom_log_formatting =
  501 
  502 ## default_file_view: "log", "co", or "markup"
  503 ## Controls whether the default view for file URLs is a checkout view or
  504 ## a log view. "log" is the default for backwards compatibility with old
  505 ## ViewCVS URLs, but "co" has the advantage that it allows ViewVC to serve
  506 ## static HTML pages directly from a repository with working links
  507 ## to other repository files
  508 ##
  509 ## NOTE: Changing this option may break compatibility with existing
  510 ## bookmarked URLs.
  511 ##
  512 ## ALSO NOTE: If you choose one of the "co" or "markup" views, be sure
  513 ## to enable it (via the allowed_views option)
  514 ##
  515 #default_file_view = log
  516 
  517 ## http_expiration_time: Expiration time (in seconds) for cacheable
  518 ## pages served by ViewVC.  Note that in most cases, a cache aware
  519 ## client will only revalidate the page after it expires (using the
  520 ## If-Modified-Since and/or If-None-Match headers) and that browsers
  521 ## will also revalidate the page when the reload button is pressed.
  522 ## Set to 0 to disable the transmission of these caching headers.
  523 ##
  524 #http_expiration_time = 600
  525 
  526 ## generate_etags: Generate Etag headers for relevant pages to assist
  527 ## in browser caching.
  528 ##   1      Generate Etags
  529 ##   0      Don't generate Etags
  530 ##
  531 #generate_etags = 1
  532 
  533 ## svn_ignore_mimetype: Don't consult the svn:mime-type property to
  534 ## determine how to display a file in the markup view.  This is
  535 ## especially helpful when versioned images carry the default
  536 ## Subversion-calculated MIME type of "application/octet-stream" (which
  537 ## isn't recognized as viewable type by browsers).
  538 ##
  539 #svn_ignore_mimetype = 0
  540 
  541 ## max_filesize_kbytes: Limit ViewVC's processing of file contents in
  542 ## "markup" and "annotate" views to only those files which are smaller
  543 ## than this setting, expressed in kilobytes.  Set to 0 to disable
  544 ## this safeguard.
  545 ##
  546 ## NOTE: The "co" and "tar" views are unaffected by this setting.
  547 ## 
  548 #max_filesize_kbytes = 512
  549 
  550 ## svn_config_dir: Path of the Subversion runtime configuration
  551 ## directory ViewVC should consult for various things, including cached
  552 ## remote authentication credentials.  If unset, Subversion will use
  553 ## the default location(s) ($HOME/.subversion, etc.)
  554 ##
  555 #svn_config_dir = 
  556 
  557 ## use_rcsparse: Use the rcsparse Python module to retrieve CVS
  558 ## repository information instead of invoking rcs utilities [EXPERIMENTAL]
  559 ##
  560 #use_rcsparse = 0
  561 
  562 ## sort_by: File sort order
  563 ##   file   Sort by filename
  564 ##   rev    Sort by revision number
  565 ##   date   Sort by commit date
  566 ##   author Sort by author
  567 ##   log    Sort by log message
  568 ##
  569 #sort_by = file
  570 
  571 ## sort_group_dirs: Group directories when sorting
  572 ##   1      Group directories together
  573 ##   0      No grouping -- sort directories as any other item would be sorted
  574 ##
  575 #sort_group_dirs = 1
  576 
  577 ## hide_attic: Hide or show the contents of the Attic subdirectory
  578 ##   1      Hide dead files inside Attic subdir
  579 ##   0      Show the files which are inside the Attic subdir
  580 ##
  581 #hide_attic = 1
  582 
  583 ## hide_errorful_entries: Hide or show errorful directory entries
  584 ## (perhaps due to not being readable, or some other rlog parsing
  585 ## error, etc.)
  586 ##   1      Hide errorful entries from the directory display
  587 ##   0      Show errorful entries (with their errors) in the directory display
  588 ##
  589 #hide_errorful_entries = 0
  590 
  591 ## log_sort: Sort order for log messages
  592 ##   date   Sort revisions by date
  593 ##   rev    Sort revision by revision number
  594 ##   none   Use the version control system's ordering
  595 ##
  596 #log_sort = date
  597 
  598 ## diff_format: Default diff format
  599 ##   h      Human readable
  600 ##   u      Unified diff
  601 ##   c      Context diff
  602 ##   s      Side by side
  603 ##   l      Long human readable (more context)
  604 ##   f      Full human readable (entire file)
  605 ##
  606 #diff_format = h
  607 
  608 ## hr_breakable: Diff view line breaks
  609 ##   1     lines break at spaces
  610 ##   0     no line breaking
  611 ## Or, use a positive integer > 1 to cut lines after that many characters
  612 ##
  613 #hr_breakable = 1
  614 
  615 ## hr_funout: Give out function names in human readable diffs.
  616 ## (Only works well for C source files, otherwise diff's heuristic falls short.)
  617 ## ('-p' option to diff)
  618 ##
  619 #hr_funout = 1
  620 
  621 ## hr_ignore_white: Ignore whitespace (indendation and stuff) for human
  622 ## readable diffs.
  623 ## ('-w' option to diff)
  624 ##
  625 #hr_ignore_white = 0
  626 
  627 ## hr_ignore_keyword_subst: Ignore diffs which are caused by keyword
  628 ## substitution (such as "$Id - Stuff").
  629 ## ('-kk' option to rcsdiff)
  630 ##
  631 #hr_ignore_keyword_subst = 1
  632 
  633 ## hr_intraline: Enable highlighting of intraline changes in human
  634 ## readable diffs.  [Requires Python 2.4]
  635 ##
  636 #hr_intraline = 0
  637 
  638 ## allow_compress: Allow compression via gzip of output if the Browser
  639 ## accepts it (HTTP_ACCEPT_ENCODING contains "gzip").
  640 ##
  641 ## NOTE: this relies on Python's gzip module, which has proven to be
  642 ## not-so-performant.  Enabling this feature should reduce the overall
  643 ## transfer size of ViewVC's responses to the client's request, but
  644 ## will do so with a speed penalty.
  645 ##
  646 #allow_compress = 0
  647 
  648 ## template_dir: The directory which contains the EZT templates used by
  649 ## ViewVC to customize the display of the various output views.  ViewVC
  650 ## looks in this directory for files with names that match the name of
  651 ## the view ("log", "directory", etc.) plus the ".ezt" extension.  If
  652 ## specified as a relative path, it is relative to the directory where
  653 ## this config file resides; absolute paths may be used as well.  If
  654 ## %lang% occurs in the pathname, then the selected language will be
  655 ## substituted.
  656 ## 
  657 ## SEE ALSO: the [templates] configuration section, where you can
  658 ## override templates on a per-view basis.
  659 ##
  660 ## Example:
  661 ## template_dir = templates/classic
  662 ## template_dir = templates/default
  663 ## template_dir = /opt/custom-viewvc-templates/templates
  664 #
  665 #template_dir = templates/default
  666 
  667 ## docroot: Web path to a directory that contains ViewVC static files
  668 ## (stylesheets, images, etc.)  If set, static files will get
  669 ## downloaded directory from this location.  If unset, static files
  670 ## will be served by the ViewVC script (at a likely performance
  671 ## penalty, and from the "docroot" subdirectory of the directory
  672 ## specified by the "template_dir" option).
  673 ##
  674 ## NOTE: This option is evaluated outside the context of a particular
  675 ## root.  Be careful when using per-root configuration to select an
  676 ## alternate template set as the default value for this option will
  677 ## still be based on the global default template set per 'template_dir'
  678 ## above, not on 'template_dir' as overridden for a given root.
  679 ##
  680 #docroot = 
  681 
  682 ## show_subdir_lastmod: Show last changelog message for CVS subdirectories
  683 ##
  684 ## NOTE: The current implementation makes many assumptions and may show
  685 ## the incorrect file at some times. The main assumption is that the
  686 ## last modified file has the newest filedate. But some CVS operations
  687 ## touches the file without even when a new version is not checked in,
  688 ## and TAG based browsing essentially puts this out of order, unless
  689 ## the last checkin was on the same tag as you are viewing.  Enable
  690 ## this if you like the feature, but don't rely on correct results.
  691 ##
  692 ## SECURITY WARNING: Enabling this will currently leak unauthorized
  693 ## path names.
  694 ##
  695 #show_subdir_lastmod = 0
  696 
  697 ## show_roots_lastmod: In the root listing view, show the most recent
  698 ## modifications made to the root.  (Subversion roots only.)
  699 ##
  700 ## NOTE: Enabling this feature will significantly reduce the
  701 ## performance of the root listing view.
  702 ##
  703 #show_roots_lastmod = 0
  704 
  705 ## show_logs: Show the most recent log entry in directory listings.
  706 ##
  707 #show_logs = 1
  708 
  709 ## show_log_in_markup: Show log when viewing file contents.
  710 ##
  711 #show_log_in_markup = 1
  712 
  713 ## cross_copies: Cross filesystem copies when traversing Subversion
  714 ## file revision histories.
  715 ##
  716 #cross_copies = 1
  717 
  718 ## use_localtime: Display dates as UTC or in local time zone.
  719 ##
  720 #use_localtime = 0
  721 
  722 ## iso8601_dates: Display timestamps using a standard ISO-8601 format.
  723 ##
  724 #iso8601_timestamps = 0
  725 
  726 ## short_log_len: The length (in characters) to which the most recent
  727 ## log entry should be truncated when shown in the directory view.
  728 ##
  729 #short_log_len = 80
  730 
  731 ## enable_syntax_coloration: Should we colorize known file content
  732 ## syntaxes?
  733 ##
  734 ## NOTE: This feature requires the Pygments Python module
  735 ## (http://pygments.org) and works only when ViewVC can determine the
  736 ## MIME content type of the file whose contents it wishes to colorize.
  737 ## Use the 'mime_types_files' configuration option to specify MIME
  738 ## type mapping files useful for making that determination.
  739 ##
  740 #enable_syntax_coloration = 1
  741 
  742 ## tabsize: The number of spaces into which horizontal tab characters
  743 ## are converted when viewing file contents.  Set to 0 to preserve
  744 ## tab characters.
  745 ##
  746 #tabsize = 8
  747 
  748 ## detect_encoding: Should we attempt to detect versioned file
  749 ## character encodings?  [Requires 'chardet' module, and is currently
  750 ## used only for the 'markup' and 'annotate' views.]
  751 ##
  752 #detect_encoding = 0
  753 
  754 ## use_cvsgraph: Use CvsGraph to offer visual graphs of CVS revision history.
  755 ##
  756 #use_cvsgraph = 0
  757 
  758 ## cvsgraph_conf: Location of the customized cvsgraph configuration file.
  759 ## May be specified as an absolute path or as a path relative to this
  760 ## configuration file.
  761 ##
  762 #cvsgraph_conf = cvsgraph.conf
  763 
  764 ## allowed_cvsgraph_useropts: A list of settings used for cvsgraph's
  765 ## user-modifiable behavior which can be changed in the graph display.
  766 ## This value is a comma-delimited list of features, taken from the
  767 ## following set:
  768 ##   invert     - Display graph upside down
  769 ##   branchbox  - Add a branchbox at the tip of each branch
  770 ##   show       - Display user-selected classes of revisions
  771 ##   rotate     - Draw the tree left-to-right or top-to-bottom [*]
  772 ##   limittags  - Allow limit on the maximum number of tags displayed
  773 ##
  774 ## If this option is left unset, users will not be permitted to modify
  775 ## the graph display behavior.
  776 ##
  777 ## [*] WARNING: The 'rotate' option is known to cause some browsers to
  778 ## crash due, presumably, to the display of excessively wide images.
  779 ##
  780 ## Example:
  781 ## allowed_cvsgraph_useropts = limittags, show
  782 ##
  783 ##
  784 #allowed_cvsgraph_useropts = 
  785 
  786 ## use_re_search: Enable regular expression search of files in a directory.
  787 ##
  788 ## WARNING: Enabling this option can consume HUGE amounts of server
  789 ## time. A "checkout" must be performed on *each* file in a directory,
  790 ## and the result needs to be searched for a match against the regular
  791 ## expression.
  792 ##
  793 ## SECURITY WARNING: Since a user can enter the regular expression, it
  794 ## is possible for them to enter an expression with many alternatives
  795 ## and a lot of backtracking. Executing that search over thousands of
  796 ## lines over dozens of files can easily tie up a server for a long
  797 ## period of time.  This option should only be used on sites with
  798 ## trusted users. It is highly inadvisable to use this on a public site.
  799 ##
  800 #use_re_search = 0
  801 
  802 ## dir_pagesize: Maximum number of directory entries on a given page.
  803 ## This allows ViewVC to present discrete pages to the users instead of
  804 ## the entire directory.  Set to 0 to disable pagination.
  805 ##
  806 #dir_pagesize = 0
  807 
  808 ## log_pagesize: Maximum number of revision log entries on a given page.
  809 ## This allows ViewVC to present discrete pages to the users instead of
  810 ## the entire revision log.  Set to 0 to disable pagination.
  811 ##
  812 #log_pagesize = 0
  813 
  814 ## log_pagesextra: Maximum number of extra pages (based on
  815 ## log_pagesize) of revision log data to fetch and present to the user
  816 ## as additional options for display.  Revision log information
  817 ## "beyond" this window is still accessible, but must be navigated to
  818 ## in multiple steps.
  819 ##
  820 ## Example:
  821 ## log_pagesize = 100
  822 ## log_pagesextra = 3
  823 ##
  824 ## For a versioned file with 1000 revisions, the above settings would
  825 ## present to the user the first 100 of those 1000 revisions, with
  826 ## links to three additional pages (the 200-299th revisions, 300-399th
  827 ## revisions, and 400-499th revisions) plus a link to the 500th
  828 ## revision.  Following these links slides the display "window",
  829 ## showing the requested set of revisions plus links to three
  830 ## additional pages beyond those, and so on.
  831 ##
  832 #log_pagesextra = 3
  833 
  834 ## limit_changes: Maximum number of changed paths shown per commit in
  835 ## the Subversion revision view and in query results. This is not a
  836 ## hard limit (the UI provides options to show all changed paths), but
  837 ## it prevents ViewVC from generating enormous and hard to read pages
  838 ## by default when they happen to contain import or merge commits
  839 ## affecting hundreds or thousands of files.  Set to 0 to disable the
  840 ## limit.
  841 ##
  842 #limit_changes = 100
  843 
  844 ## stacktraces: If set, exception stack traces will be displayed in full
  845 ## (where so dictated by the templating system).  Otherwise, only the
  846 ## top-most exception will be display.  Stack traces can carry system
  847 ## paths, revealing information about the server that administrators
  848 ## would prefer not to share.
  849 ##
  850 #stacktraces = 0
  851 
  852 ##---------------------------------------------------------------------------
  853 [templates]
  854 
  855 ## You can override the templates used by various ViewVC views in this
  856 ## section.  By default, ViewVC will look for templates in the
  857 ## directory specified by the "template_dir" configuration option (see
  858 ## the documentation for that option for details).  But if you want to
  859 ## use a different template for a particular view, simply uncomment the
  860 ## appropriate option below and specify the currect location of the EZT
  861 ## template file you wish to use for that view.
  862 ## 
  863 ## Templates are specified relative to the configured template
  864 ## directory (see the "template_dir" option), but absolute paths may
  865 ## also be used as well.
  866 ##
  867 ## If %lang% occurs in the pathname, then the selected language will be
  868 ## substituted.
  869 ##
  870 ## NOTE: the selected language is defined by the "languages" item in the
  871 ##       [general] section, and based on the request's Accept-Language
  872 ##       header.
  873 ##
  874 
  875 ## diff: Template used for the file differences view.
  876 ##
  877 #diff = 
  878 
  879 ## directory: Template used for the directory listing view.
  880 ##
  881 #directory = 
  882 
  883 ## error: Template used for the ViewVC error display view.
  884 ##
  885 #error = 
  886 
  887 ## file: Template used for the file contents/annotation view.
  888 ##
  889 #file = 
  890 
  891 ## graph: Template used for the revision graph view.
  892 ##
  893 #graph = 
  894 
  895 ## log: Template used for the revision log view.
  896 ##
  897 #log = 
  898 
  899 ## query_form: Template used for the query form view.
  900 ##
  901 #query_form = 
  902 
  903 ## query_results: Template used for the query results view.
  904 ##
  905 #query_results = 
  906 
  907 ## revision: Template used for the revision/changeset view.
  908 ##
  909 #revision = 
  910 
  911 ## roots: Template used for the root listing view.
  912 ##
  913 #roots = 
  914 
  915 ##---------------------------------------------------------------------------
  916 [cvsdb]
  917 
  918 ## enabled: Enable database integration feature.
  919 ##
  920 #enabled = 0
  921 
  922 ## host: Database hostname.  Leave unset to use a local Unix socket
  923 ## connection.
  924 ##
  925 #host = 
  926 
  927 ## post: Database listening port.
  928 ##
  929 #port = 3306
  930 
  931 ## database_name: ViewVC database name.
  932 ##
  933 #database_name = ViewVC
  934 
  935 ## user: Username of user with read/write privileges to the database
  936 ## specified by the 'database_name' configuration option.
  937 ##
  938 #user = 
  939 
  940 ## passwd: Password of user with read/write privileges to the database
  941 ## specified by the 'database_name' configuration option.
  942 ##
  943 #passwd = 
  944 
  945 ## readonly_user: Username of user with read privileges to the database
  946 ## specified by the 'database_name' configuration option.
  947 ##
  948 #readonly_user = 
  949 
  950 ## readonly_passwd: Password of user with read privileges to the database
  951 ## specified by the 'database_name' configuration option.
  952 ##
  953 #readonly_passwd = 
  954 
  955 ## row_limit: Maximum number of rows returned by a given normal query
  956 ## to the database.
  957 ##
  958 ## NOTE: This limits the amount of data provided to ViewVC by the
  959 ## database.  It is from this already-reduced data set that ViewVC
  960 ## builds the query response it presents to the user, which may or may
  961 ## not include still more limiting via the query form's 'limit'
  962 ## parameter.  In other words, there is no value which the user can use
  963 ## in the query form's 'limit' parameter which will cause more data to
  964 ## be returned by the database for ViewVC to process.
  965 ##
  966 #row_limit = 1000
  967 
  968 ## rss_row_limit: Maximum number of rows returned by a given query to
  969 ## the database made as part of an RSS feed request.  (Keeping in mind
  970 ## that RSS readers tend to poll regularly for new data, you might want
  971 ## to keep this set to a conservative number.)
  972 ##
  973 ## See also the `NOTE' for the 'row_limit' option, which applies here
  974 ## as well.
  975 ##
  976 #rss_row_limit = 100
  977 
  978 ## check_database_for_root: Check if the repository is found in the
  979 ## database before showing the query link and RSS feeds.
  980 ## 
  981 ## WARNING: Enabling this check adds the cost of a database connection
  982 ## and query to most ViewVC requests.  If all your roots are represented
  983 ## in the commits database, or if you don't care about the creation of
  984 ## RSS and query links that might lead ultimately to error pages for
  985 ## certain of your roots, or if you simply don't want to add this extra
  986 ## cost to your ViewVC requests, leave this disabled.
  987 ##
  988 #check_database_for_root = 0
  989 
  990 ##---------------------------------------------------------------------------
  991 [vhosts]
  992 
  993 ## Virtual hosts are individual logical servers accessible via
  994 ## different hostnames, but which are all really the same physical
  995 ## computer.  For example, you might have your web server configured to
  996 ## accept incoming traffic for both http://www.yourdomain.com/ and
  997 ## http://viewvc.yourdomain.com/.  Users pointing their web browsers at
  998 ## each of those two URLs might see entirely different content via one
  999 ## URL versus the other, but all that content actually lives on the
 1000 ## same computer, is served up via the same web server, and so
 1001 ## on.  It just *looks* like its coming from multiple servers.
 1002 ##
 1003 ## ViewVC allows you to customize its configuration options for
 1004 ## individual virtual hosts.  You might, for example, wish to expose
 1005 ## all of your Subversion repositories at http://svn.yourdomain.com/viewvc/ 
 1006 ## and all your CVS ones at http://cvs.yourdomain.com/viewvc/, with no
 1007 ## cross-exposure.  Using ViewVC's virtual host (vhost) configuration
 1008 ## support, you can do this.  Simply create two vhost configurations
 1009 ## (one for each of your hostnames), then configure the cvs_roots
 1010 ## option only for the vhost associated with cvs.yourdomain.com, and
 1011 ## configure the svn_roots option only for the vhost associated with
 1012 ## svn.yourdomain.com.
 1013 ##
 1014 ## This section is a freeform configuration section, where you create
 1015 ## both the option names and their values.  The names of the options
 1016 ## are then treated as canonical names of virtual hosts, and their
 1017 ## values are defined to be comma-delimited lists of hostname globs
 1018 ## against which incoming ViewVC requests will be matched to figure out
 1019 ## which vhost they apply to.
 1020 ##
 1021 ## After you've named and defined your vhosts, you may then create new
 1022 ## configuration sections whose names are of the form
 1023 ## "vhost-VHOSTNAME|CONFIGSECTION".  VHOSTNAME here is the canonical name
 1024 ## of one of the virtual hosts you defined under the [vhosts] section.
 1025 ## Inside those configuration sections, you override the standard
 1026 ## ViewVC options typically found in the base configuration section
 1027 ## named CONFIGSECTION ("general", "option", etc.)
 1028 ##
 1029 ## NOTE: Per-vhost overrides may only be applied to the following
 1030 ## sections:
 1031 ##
 1032 ##    general
 1033 ##    options
 1034 ##    utilities
 1035 ##    templates
 1036 ##    cvsdb
 1037 ##    authz-*
 1038 ##
 1039 ## Here is an example:
 1040 ##
 1041 ##    [vhosts]
 1042 ##    libs = libs.yourdomain.*, *.yourlibs.*
 1043 ##    gui = guiproject.yourdomain.*
 1044 ##
 1045 ##    [vhost-libs|general]
 1046 ##    cvs_roots = 
 1047 ##    svn_roots = svnroot: /var/svn/libs-repos
 1048 ##    default_root = svnroot
 1049 ##
 1050 ##    [vhost-libs|options]
 1051 ##    show_logs = 1
 1052 ##
 1053 ##    [vhost-gui|general]
 1054 ##    cvs_roots = cvsroot: /var/cvs/guiproject
 1055 ##    svn_roots = 
 1056 ##    default_root = cvsroot
 1057 ##
 1058 
 1059 ##---------------------------------------------------------------------------
 1060 ## ViewVC recognizes per-root configuration overrides, too.  To
 1061 ## override the value of a configuration parameter only for a single
 1062 ## root, create a configuration section whose names is of the form
 1063 ## "root-ROOTNAME|CONFIGSECTION".  ROOTNAME here is the name of the root
 1064 ## as defined explicitly in cvs_roots or svn_roots or implicitly as the
 1065 ## basename of a root path in root_parents.  Options found in this new
 1066 ## configuration section override for this one root the corresponding
 1067 ## options found in the base configuration section CONFIGSECTION
 1068 ## ("options", "authz-*", etc.) as interpreted after per-vhost
 1069 ## overrides (if any) have been applied.
 1070 ##
 1071 ## NOTE: Per-root overrides may only be applied to the following
 1072 ## sections:
 1073 ##
 1074 ##    options
 1075 ##    utilities
 1076 ##    authz-*
 1077 ##
 1078 ## WARNING: Do not use per-root overrides if your ViewVC instance is
 1079 ## served via the standalone.py server option!  Doing so could cause
 1080 ## ViewVC to be unable to function properly (or at all).
 1081 ##
 1082 ## Here is an example showing how to enable Subversion authz-based
 1083 ## authorization for only the single root named "svnroot":
 1084 ## 
 1085 ##    [root-svnroot|options]
 1086 ##    authorizer = svnauthz
 1087 ##
 1088 ##    [root-svnroot|authz-svnauthz]
 1089 ##    authzfile = /path/to/authzfile
 1090 ##
 1091 ## If your root names include context, you can specify that, too:
 1092 ##
 1093 ##    [root-project/svnroot|options]
 1094 ##    authorizer = svnauthz
 1095 ##
 1096 ##    [root-project/svnroot|authz-svnauthz]
 1097 ##    authzfile = /path/to/authzfile
 1098 
 1099 ##---------------------------------------------------------------------------
 1100 [authz-forbidden]
 1101 
 1102 ## The "forbidden" authorizer forbids access to repository modules,
 1103 ## defined to be top-level subdirectories in a repository.
 1104 ##
 1105 ## NOTE: The options in this section apply only when the 'authorizer'
 1106 ## option (in the [options] section) is set to 'forbidden'.
 1107 
 1108 ## forbidden: A comma-delimited list of patterns which match modules
 1109 ## that ViewVC should hide from users.
 1110 ##
 1111 ## You can use a simple list of modules, or something more complex:
 1112 ##
 1113 ##   *) The "!" can be used before a module to explicitly state that it
 1114 ##      is NOT forbidden. Whenever this form is seen, then all modules will
 1115 ##      be forbidden unless one of the "!" modules match.
 1116 ##
 1117 ##   *) Shell-style "glob" expressions may be used. "*" will match any
 1118 ##      sequence of zero or more characters, "?" will match any single
 1119 ##      character, "[seq]" will match any character in seq, and "[!seq]"
 1120 ##      will match any character not in seq.
 1121 ##
 1122 ##   *) Tests are performed in sequence. The first match will terminate the
 1123 ##      testing. This allows for more complex allow/deny patterns.
 1124 ##
 1125 ## Tests are case-sensitive.
 1126 ##
 1127 ## NOTE: Again, this is for the hiding of modules within repositories, *not* 
 1128 ## for the hiding of repositories (roots) themselves.
 1129 ##
 1130 ## Some examples:
 1131 ##
 1132 ##    Disallow "example" but allow all others:
 1133 ##       forbidden = example
 1134 ##
 1135 ##    Disallow "example1" and "example2" but allow all others:
 1136 ##       forbidden = example1, example2
 1137 ##
 1138 ##    Allow *only* "example1" and "example2":
 1139 ##       forbidden = !example1, !example2
 1140 ##
 1141 ##    Forbid modules starting with "x":
 1142 ##       forbidden = x*
 1143 ##
 1144 ##    Allow modules starting with "x" but no others:
 1145 ##       forbidden = !x*
 1146 ##
 1147 ##    Allow "xml", forbid other modules starting with "x", and allow the rest:
 1148 ##       forbidden = !xml, x*, !*
 1149 ##
 1150 #forbidden = 
 1151 
 1152 ##---------------------------------------------------------------------------
 1153 [authz-forbiddenre]
 1154 
 1155 ## The "forbiddenre" authorizer forbids access to repositories and
 1156 ## repository paths by comparing a list of regular expressions
 1157 ## (separated by commas) against paths consisting of the repository (or
 1158 ## root) name plus the path of the versioned file or directory to be
 1159 ## tested.  For example, to see if the user is authorized to see the
 1160 ## path "/trunk/www/index.html" in the repository whose root name is
 1161 ## "svnrepos", this authorizer will check the path
 1162 ## "svnrepos/trunk/www/index.html" against the list of forbidden
 1163 ## regular expressions.  Directory paths will be terminated by a forward
 1164 ## slash.
 1165 ##
 1166 ## NOTE: The options in this section apply only when the 'authorizer'
 1167 ## option (in the [options] section) is set to 'forbiddenre'.
 1168 
 1169 ## forbiddenre: A comma-delimited list of regular expressions which
 1170 ## match paths that ViewVC should hide from users.
 1171 ##
 1172 ## Like the "forbidden" authorizer...
 1173 ##
 1174 ##   *) The "!" can be used before a module to explicitly state that it
 1175 ##      is NOT forbidden. Whenever this form is seen, then all modules will
 1176 ##      be forbidden unless one of the "!" modules match.
 1177 ##
 1178 ##   *) Tests are performed in sequence. The first match will terminate the
 1179 ##      testing. This allows for more complex allow/deny patterns.
 1180 ##
 1181 ## Unlike the "forbidden" authorizer, you can can use this to hide roots, too.
 1182 ##
 1183 ## Some examples:
 1184 ##
 1185 ##    Disallow files named "PRIVATE", but allow all others:
 1186 ##       forbiddenre = /PRIVATE$
 1187 ##
 1188 ##    Disallow the "hidden" repository, allowing all others:
 1189 ##       forbiddenre = ^hidden(/|$)
 1190 ##
 1191 ##    Allow only the "example1" and "example2" roots and the paths inside them,
 1192 ##    disallowing all others (which can be done in multiple ways):
 1193 ##       forbiddenre = !^example1(/|$), !^example2(/|$)/
 1194 ##       forbiddenre = !^example[12](/|$)
 1195 ##
 1196 ##    Only allow visibility of HTML files and the directories that hold them:
 1197 ##       forbiddenre = !^([^/]+|.*(/|\.html))$
 1198 ##
 1199 #forbiddenre = 
 1200 
 1201 ##---------------------------------------------------------------------------
 1202 [authz-svnauthz]
 1203 
 1204 ## The "svnauthz" authorizer uses a Subversion authz configuration file
 1205 ## to determine access to repository paths.
 1206 ##
 1207 ## NOTE: The options in this section apply only when the 'authorizer'
 1208 ## option (in the [options] section) is set to 'svnauthz'.
 1209 
 1210 ## authzfile: Specifies the location of the authorization rules file
 1211 ## (using an absolute path).
 1212 ##
 1213 #authzfile =
 1214 
 1215 ## root_relative_authzfile: Specifies the location of the
 1216 ## authorization rules file using an path relative to the repository.
 1217 ##
 1218 ## Example:
 1219 ## root_relative_authzfile = conf/access
 1220 ##
 1221 #root_relative_authzfile = 
 1222 
 1223 ## force_username_case: Like the AuthzForceUsernameCase httpd.conf
 1224 ## directive, set this to "upper" or "lower" to force the normalization
 1225 ## to upper- or lower-case, respectively, of incoming usernames prior
 1226 ## to comparison against the authorization rules files.  Leave the
 1227 ## option unset to preserve the username case.
 1228 ##
 1229 #force_username_case = 
 1230 
 1231 ##---------------------------------------------------------------------------