Mercurial > p > roundup > code
comparison doc/installation.txt @ 2945:98efa80f0f90
added mod_python options TrackerDebug and TrackerTiming
| author | Alexander Smishlajev <a1s@users.sourceforge.net> |
|---|---|
| date | Mon, 22 Nov 2004 08:29:49 +0000 |
| parents | ad4fb8a14a97 |
| children | dd558120d927 |
comparison
equal
deleted
inserted
replaced
| 2944:835ac4013578 | 2945:98efa80f0f90 |
|---|---|
| 443 receive OS environment variables in the same way as command-line | 443 receive OS environment variables in the same way as command-line |
| 444 programs, so the language cannot be selected by setting commonly | 444 programs, so the language cannot be selected by setting commonly |
| 445 used variables like ``LANG`` or ``LC_ALL``. ``TrackerLanguage`` | 445 used variables like ``LANG`` or ``LC_ALL``. ``TrackerLanguage`` |
| 446 value has the same syntax as values of these environment variables. | 446 value has the same syntax as values of these environment variables. |
| 447 This option may be omitted. | 447 This option may be omitted. |
| 448 | |
| 449 TrackerDebug: | |
| 450 run the tracker in debug mode. Setting this option to ``yes`` or | |
| 451 ``true`` has the same effect as running ``roundup-server -t debug``: | |
| 452 the database schema and used html templates are rebuilt for each | |
| 453 HTTP request. Values ``no`` or ``false`` mean that all html | |
| 454 templates for the tracker are compiled and the database schema is | |
| 455 checked once at startup. This is the default behaviour. | |
| 456 | |
| 457 TrackerTiming: | |
| 458 has nearly the same effect as environment variable ``CGI_SHOW_TIMING`` | |
| 459 for standalone roundup server. The difference is that setting this | |
| 460 option to ``no`` or ``false`` disables timings display. Value | |
| 461 ``comment`` writes request handling times in html comment, and | |
| 462 any other non-empty value makes timing report visible. By default, | |
| 463 timing display is disabled. | |
| 448 | 464 |
| 449 In the following example we have two trackers set up in | 465 In the following example we have two trackers set up in |
| 450 ``/var/db/roundup/support`` and ``var/db/roundup/devel`` and accessed | 466 ``/var/db/roundup/support`` and ``var/db/roundup/devel`` and accessed |
| 451 as ``https://my.host/roundup/support/`` and ``https://my.host/roundup/devel/`` | 467 as ``https://my.host/roundup/support/`` and ``https://my.host/roundup/devel/`` |
| 452 respectively. Having them share same parent directory allows us to | 468 respectively. Having them share same parent directory allows us to |