Changes between Version 1 and Version 2 of TracStandalone


Ignore:
Timestamp:
05/16/23 10:08:46 (12 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracStandalone

    v1 v2  
    1 ** Note: this page documents the version 1.0 of Trac, see [[0.12/TracStandalone]] if you need the previous version **
    2 = Tracd =
     1= Tracd
    32
    43Tracd is a lightweight standalone Trac web server.
    54It can be used in a variety of situations, from a test or development server to a multiprocess setup behind another web server used as a load balancer.
    65
    7 == Pros ==
    8 
    9  * Fewer dependencies: You don't need to install apache or any other web-server.
    10  * Fast: Should be almost as fast as the [wiki:TracModPython mod_python] version (and much faster than the [wiki:TracCgi CGI]), even more so since version 0.12 where the HTTP/1.1 version of the protocol is enabled by default
    11  * Automatic reloading: For development, Tracd can be used in ''auto_reload'' mode, which will automatically restart the server whenever you make a change to the code (in Trac itself or in a plugin).
    12 
    13 == Cons ==
     6== Pros
     7
     8 * Fewer dependencies: You don't need to install Apache or any other web-server.
     9 * Fast: Should be almost as fast as the [wiki:TracModWSGI mod_wsgi] version (and much faster than the [wiki:TracCgi CGI]), especially since the HTTP/1.1 version of the protocol is enabled by default.
     10 * Automatic reloading: For development, Tracd can be used in ''auto_reload'' mode, which will automatically restart the server whenever you make a change to the code, for example in Trac itself or in a plugin.
     11
     12== Cons
    1413
    1514 * Fewer features: Tracd implements a very simple web-server and is not as configurable or as scalable as Apache httpd.
    16  * No native HTTPS support: [http://www.rickk.com/sslwrap/ sslwrap] can be used instead,
    17    or [http://trac.edgewall.org/wiki/STunnelTracd stunnel -- a tutorial on how to use stunnel with tracd] or Apache with mod_proxy.
    18 
    19 == Usage examples ==
     15
     16== Usage examples
    2017
    2118A single project on port 8080. (http://localhost:8080/)
    22 {{{
     19{{{#!sh
    2320 $ tracd -p 8080 /path/to/project
    2421}}}
    25 Stricly speaking this will make your Trac accessible to everybody from your network rather than ''localhost only''. To truly limit it use ''--hostname'' option.
    26 {{{
     22Strictly speaking this will make your Trac accessible to everybody from your network rather than ''localhost only''. To truly limit it use the `--hostname` option.
     23{{{#!sh
    2724 $ tracd --hostname=localhost -p 8080 /path/to/project
    2825}}}
    2926With more than one project. (http://localhost:8080/project1/ and http://localhost:8080/project2/)
    30 {{{
     27{{{#!sh
    3128 $ tracd -p 8080 /path/to/project1 /path/to/project2
    3229}}}
    3330
    34 You can't have the last portion of the path identical between the projects since Trac uses that name to keep the URLs of the
    35 different projects unique. So if you use `/project1/path/to` and `/project2/path/to`, you will only see the second project.
     31You can't have the last portion of the path identical between the projects since Trac uses that name to keep the URLs of the different projects unique. So if you use `/project1/path/to` and `/project2/path/to`, you will only see the second project.
    3632
    3733An alternative way to serve multiple projects is to specify a parent directory in which each subdirectory is a Trac project, using the `-e` option. The example above could be rewritten:
    38 {{{
     34{{{#!sh
    3935 $ tracd -p 8080 -e /path/to
    4036}}}
    4137
    42 To exit the server on Windows, be sure to use {{{CTRL-BREAK}}} -- using {{{CTRL-C}}} will leave a Python process running in the background.
    43 
    44 == Installing as a Windows Service ==
    45 
    46 === Option 1 ===
    47 To install as a Windows service, get the [http://www.google.com/search?q=srvany.exe SRVANY] utility and run:
    48 {{{
     38There is support for the HTTPS protocol (//Since 1.3.4//). Specify the path to the PEM certificate file and keyfile using the `--certfile` and `--keyfile` options. You can specify just the `--certfile` option if you have a [https://docs.python.org/2/library/ssl.html#combined-key-and-certificate combined key and certificate].
     39
     40To exit the server on Windows, be sure to use `CTRL-BREAK`. Using `CTRL-C` will leave a Python process running in the background.
     41
     42== Installing as a Windows Service
     43
     44=== Option 1
     45
     46To install as a Windows service, get the [https://www.google.com/search?q=srvany.exe SRVANY] utility and run:
     47{{{#!cmd
    4948 C:\path\to\instsrv.exe tracd C:\path\to\srvany.exe
    50  reg add HKLM\SYSTEM\CurrentControlSet\Services\tracd\Parameters /v Application /d "\"C:\path\to\python.exe\" \"C:\path\to\python\scripts\tracd-script.py\" <your tracd parameters>"
     49 reg add HKLM\SYSTEM\CurrentControlSet\Services\tracd\Parameters /v Application /d "\"C:\path\to\python.exe\" \"C:\path\to\python\scripts\tracd.exe\" <your tracd parameters>"
    5150 net start tracd
    5251}}}
    5352
    54 '''DO NOT''' use {{{tracd.exe}}}.  Instead register {{{python.exe}}} directly with {{{tracd-script.py}}} as a parameter.  If you use {{{tracd.exe}}}, it will spawn the python process without SRVANY's knowledge.  This python process will survive a {{{net stop tracd}}}.
     53{{{#!div style="border: 1pt dotted; margin: 1em;"
     54**Attention:** Do not use `tracd.exe` directly. Instead register `python.exe` directly with `tracd.exe` as a parameter. If you use `tracd.exe`, it will spawn the Python process without SRVANY's knowledge. This Python process will survive a `net stop tracd`.
     55}}}
    5556
    5657If you want tracd to start automatically when you boot Windows, do:
    57 {{{
     58{{{#!cmd
    5859 sc config tracd start= auto
    5960}}}
    … …  
    6667
    6768Three (string) parameters are provided:
    68 ||!AppDirectory ||C:\Python26\ ||
     69||!AppDirectory ||C:\Python27\ ||
    6970||Application ||python.exe ||
    70 ||!AppParameters ||scripts\tracd-script.py -p 8080 ... ||
    71 
    72 Note that, if the !AppDirectory is set as above, the paths of the executable ''and'' of the script name and parameter values are relative to the directory.  This makes updating Python a little simpler because the change can be limited, here, to a single point.
    73 (This is true for the path to the .htpasswd file, as well, despite the documentation calling out the /full/path/to/htpasswd; however, you may not wish to store that file under the Python directory.)
    74 }}}
    75 
    76 For Windows 7 User, srvany.exe may not be an option, so you can use [http://www.google.com/search?q=winserv.exe WINSERV] utility and run:
    77 {{{
    78 "C:\path\to\winserv.exe" install tracd -displayname "tracd" -start auto "C:\path\to\python.exe" c:\path\to\python\scripts\tracd-script.py <your tracd parameters>"
    79 
     71||!AppParameters ||scripts\tracd.exe -p 8080 ... ||
     72
     73Note that, if the !AppDirectory is set as above, the paths of the executable ''and'' of the script name and parameter values are relative to the directory. This makes updating Python a little simpler because the change can be limited, here, to a single point.
     74This is true for the path to the .htpasswd file as well, despite the documentation calling out the /full/path/to/htpasswd; however, you may not wish to store that file under the Python directory.
     75}}}
     76
     77For Windows 7 User, srvany.exe may not be an option, so you can use [https://www.google.com/search?q=winserv.exe WINSERV] utility and run:
     78{{{#!cmd
     79"C:\path\to\winserv.exe" install tracd -displayname "tracd" -start auto "C:\path\to\python.exe" c:\path\to\python\scripts\tracd.exe <your tracd parameters>"
    8080net start tracd
    8181}}}
    8282
    83 === Option 2 ===
    84 
    85 Use [http://trac-hacks.org/wiki/WindowsServiceScript WindowsServiceScript], available at [http://trac-hacks.org/ Trac Hacks]. Installs, removes, starts, stops, etc. your Trac service.
    86 
    87 === Option 3 ===
     83=== Option 2
     84
     85Use [https://trac-hacks.org/wiki/WindowsServiceScript WindowsServiceScript], available at [https://trac-hacks.org/ Trac Hacks]. Installs, removes, starts, stops, etc. your Trac service.
     86
     87=== Option 3
    8888
    8989also cygwin's cygrunsrv.exe can be used:
    90 {{{
     90{{{#!sh
    9191$ cygrunsrv --install tracd --path /cygdrive/c/Python27/Scripts/tracd.exe --args '--port 8000 --env-parent-dir E:\IssueTrackers\Trac\Projects'
    9292$ net start tracd
    9393}}}
    9494
    95 == Using Authentication ==
     95== Using Authentication
     96
     97Tracd allows you to run Trac without the need for Apache, but you can take advantage of Apache's password tools (`htpasswd` and `htdigest`) to easily create a password file in the proper format for tracd to use in authentication. It is also possible to create the password file without `htpasswd` or `htdigest`; see below for alternatives.
     98
     99{{{#!div style="border: 1pt dotted; margin: 1em"
     100**Attention:** Make sure you place the generated password files on a filesystem which supports sub-second timestamps, as Trac will monitor their modified time and changes happening on a filesystem with too coarse-grained timestamp resolution (like `ext2` or `ext3` on Linux, or HFS+ on OSX).
     101}}}
    96102
    97103Tracd provides support for both Basic and Digest authentication. Digest is considered more secure. The examples below use Digest; to use Basic authentication, replace `--auth` with `--basic-auth` in the command line.
    98104
    99105The general format for using authentication is:
    100 {{{
     106{{{#!sh
    101107 $ tracd -p port --auth="base_project_dir,password_file_path,realm" project_path
    102108}}}
    … …  
    114120Examples:
    115121
    116 {{{
     122{{{#!sh
    117123 $ tracd -p 8080 \
    118124   --auth="project1,/path/to/passwordfile,mycompany.com" /path/to/project1
    … …  
    120126
    121127Of course, the password file can be be shared so that it is used for more than one project:
    122 {{{
     128{{{#!sh
    123129 $ tracd -p 8080 \
    124130   --auth="project1,/path/to/passwordfile,mycompany.com" \
    … …  
    128134
    129135Another way to share the password file is to specify "*" for the project name:
    130 {{{
     136{{{#!sh
    131137 $ tracd -p 8080 \
    132138   --auth="*,/path/to/users.htdigest,mycompany.com" \
    … …  
    134140}}}
    135141
    136 === Basic Authorization: Using a htpasswd password file ===
     142=== Basic Authorization: Using a htpasswd password file
     143
    137144This section describes how to use `tracd` with Apache .htpasswd files.
    138145
    139   Note: It is necessary (at least with Python 2.6) to install the fcrypt package in order to
    140   decode some htpasswd formats.  Trac source code attempt an `import crypt` first, but there
    141   is no such package for Python 2.6. Only `SHA-1` passwords (since Trac 1.0) work without this module.
     146'''Note''': On Windows It is necessary to install the [https://pypi.python.org/pypi/passlib passlib] package in order to decode some htpasswd formats. Only `SHA-1` passwords (since Trac 1.0) work without this module.
    142147
    143148To create a .htpasswd file use Apache's `htpasswd` command (see [#GeneratingPasswordsWithoutApache below] for a method to create these files without using Apache):
    144 {{{
     149{{{#!sh
    145150 $ sudo htpasswd -c /path/to/env/.htpasswd username
    146151}}}
    147152then for additional users:
    148 {{{
     153{{{#!sh
    149154 $ sudo htpasswd /path/to/env/.htpasswd username2
    150155}}}
    151156
    152157Then to start `tracd` run something like this:
    153 {{{
    154  $ tracd -p 8080 --basic-auth="projectdirname,/fullpath/environmentname/.htpasswd,realmname" /fullpath/environmentname
     158{{{#!sh
     159 $ tracd -p 8080 --basic-auth="project,/fullpath/environmentname/.htpasswd,realmname" /path/to/project
    155160}}}
    156161
    157162For example:
    158 {{{
    159  $ tracd -p 8080 --basic-auth="testenv,/srv/tracenv/testenv/.htpasswd,My Test Env" /srv/tracenv/testenv
    160 }}}
    161 ''Note:'' You might need to pass "-m" as a parameter to htpasswd on some platforms (OpenBSD).
    162 
    163 === Digest authentication: Using a htdigest password file ===
    164 
    165 If you have Apache available, you can use the htdigest command to generate the password file. Type 'htdigest' to get some usage instructions, or read [http://httpd.apache.org/docs/2.0/programs/htdigest.html this page] from the Apache manual to get precise instructions.  You'll be prompted for a password to enter for each user that you create.  For the name of the password file, you can use whatever you like, but if you use something like `users.htdigest` it will remind you what the file contains. As a suggestion, put it in your <projectname>/conf folder along with the [TracIni trac.ini] file.
     163{{{#!sh
     164 $ tracd -p 8080 --basic-auth="project,/srv/tracenv/testenv/.htpasswd,My Test Env" /path/to/project
     165}}}
     166
     167'''Note:''' You might need to pass "-m" as a parameter to htpasswd on some platforms (OpenBSD).
     168
     169=== Digest authentication: Using a htdigest password file
     170
     171If you have Apache available, you can use the htdigest command to generate the password file. Type 'htdigest' to get some usage instructions, or read [https://httpd.apache.org/docs/2.0/programs/htdigest.html this page] from the Apache manual to get precise instructions.  You'll be prompted for a password to enter for each user that you create.  For the name of the password file, you can use whatever you like, but if you use something like `users.htdigest` it will remind you what the file contains. As a suggestion, put it in your <projectname>/conf folder along with the [TracIni trac.ini] file.
    166172
    167173Note that you can start tracd without the `--auth` argument, but if you click on the ''Login'' link you will get an error.
    168174
    169 === Generating Passwords Without Apache ===
    170 
    171 Basic Authorization can be accomplished via this [http://aspirine.org/htpasswd_en.html online HTTP Password generator] which also supports `SHA-1`.  Copy the generated password-hash line to the .htpasswd file on your system. Note that Windows Python lacks the "crypt" module that is the default hash type for htpasswd ; Windows Python can grok MD5 password hashes just fine and you should use MD5.
    172 
    173 You can use this simple Python script to generate a '''digest''' password file:
    174 
    175 {{{
    176 #!python
    177 from optparse import OptionParser
    178 # The md5 module is deprecated in Python 2.5
    179 try:
    180     from hashlib import md5
    181 except ImportError:
    182     from md5 import md5
    183 realm = 'trac'
    184 
    185 # build the options
    186 usage = "usage: %prog [options]"
    187 parser = OptionParser(usage=usage)
    188 parser.add_option("-u", "--username",action="store", dest="username", type = "string",
    189                   help="the username for whom to generate a password")
    190 parser.add_option("-p", "--password",action="store", dest="password", type = "string",
    191                   help="the password to use")
    192 parser.add_option("-r", "--realm",action="store", dest="realm", type = "string",
    193                   help="the realm in which to create the digest")
    194 (options, args) = parser.parse_args()
    195 
    196 # check options
    197 if (options.username is None) or (options.password is None):
    198    parser.error("You must supply both the username and password")
    199 if (options.realm is not None):
    200    realm = options.realm
    201    
    202 # Generate the string to enter into the htdigest file
    203 kd = lambda x: md5(':'.join(x)).hexdigest()
    204 print ':'.join((options.username, realm, kd([options.username, realm, options.password])))
    205 }}}
    206 
    207 Note: If you use the above script you must set the realm in the `--auth` argument to '''`trac`'''. Example usage (assuming you saved the script as trac-digest.py):
    208 
    209 {{{
    210  $ python trac-digest.py -u username -p password >> c:\digest.txt
    211  $ tracd --port 8000 --auth=proj_name,c:\digest.txt,trac c:\path\to\proj_name
     175=== Generating Passwords Without Apache
     176
     177Basic Authorization can be accomplished via this [http://aspirine.org/htpasswd_en.html online HTTP Password generator] which also supports `SHA-1`.  Copy the generated password-hash line to the .htpasswd file on your system. Note that Windows Python lacks the "crypt" module that is the default hash type for htpasswd. Windows Python can grok MD5 password hashes just fine and you should use MD5.
     178
     179Trac also provides `htpasswd` and `htdigest` scripts in [https://trac.edgewall.org/browser/trunk/contrib contrib] (also available in the tar or zip archive):
     180{{{#!sh
     181$ ./contrib/htpasswd.py -cb htpasswd user1 user1
     182$ ./contrib/htpasswd.py -b htpasswd user2 user2
     183}}}
     184
     185{{{#!sh
     186$ ./contrib/htdigest.py -cb htdigest trac user1 user1
     187$ ./contrib/htdigest.py -b htdigest trac user2 user2
    212188}}}
    213189
    214190==== Using `md5sum`
     191
    215192It is possible to use `md5sum` utility to generate digest-password file:
    216 {{{
     193{{{#!sh
    217194user=
    218195realm=
    … …  
    222199}}}
    223200
    224 == Reference ==
    225 
    226 Here's the online help, as a reminder (`tracd --help`):
     201== Reference
     202
     203Here's the online help, as a reminder (`tracd -h` or `tracd --help`):
    227204{{{
    228 Usage: tracd [options] [projenv] ...
    229 
    230 Options:
     205usage: tracd [-h] [--version] [-e PARENTDIR | -s]
     206             [-a DIGESTAUTH | --basic-auth BASICAUTH] [-p PORT] [-b HOSTNAME]
     207             [--protocol {http,https,scgi,ajp,fcgi}] [--certfile CERTFILE]
     208             [--keyfile KEYFILE] [-q] [--base-path BASE_PATH]
     209             [--http10 | --http11] [-r | -d] [--pidfile PIDFILE] [--umask MASK]
     210             [--group GROUP] [--user USER]
     211             [envs ...]
     212
     213positional arguments:
     214  envs                  path of the project environment(s)
     215
     216options:
     217  -h, --help            show this help message and exit
    231218  --version             show program's version number and exit
    232   -h, --help            show this help message and exit
    233   -a DIGESTAUTH, --auth=DIGESTAUTH
     219  -e PARENTDIR, --env-parent-dir PARENTDIR
     220                        parent directory of the project environments
     221  -s, --single-env      only serve a single project without the project list
     222  -a DIGESTAUTH, --auth DIGESTAUTH
    234223                        [projectdir],[htdigest_file],[realm]
    235   --basic-auth=BASICAUTH
     224  --basic-auth BASICAUTH
    236225                        [projectdir],[htpasswd_file],[realm]
    237   -p PORT, --port=PORT  the port number to bind to
    238   -b HOSTNAME, --hostname=HOSTNAME
     226  -p PORT, --port PORT  the port number to bind to
     227  -b HOSTNAME, --hostname HOSTNAME
    239228                        the host name or IP address to bind to
    240   --protocol=PROTOCOL   http|scgi|ajp|fcgi
    241   -q, --unquote         unquote PATH_INFO (may be needed when using ajp)
    242   --http10              use HTTP/1.0 protocol version instead of HTTP/1.1
    243   --http11              use HTTP/1.1 protocol version (default)
    244   -e PARENTDIR, --env-parent-dir=PARENTDIR
    245                         parent directory of the project environments
    246   --base-path=BASE_PATH
     229  --protocol {http,https,scgi,ajp,fcgi}
     230                        the server protocol (default: http)
     231  --certfile CERTFILE   PEM certificate file for HTTPS
     232  --keyfile KEYFILE     PEM key file for HTTPS
     233  -q, --unquote         unquote PATH_INFO (may be needed when using the ajp
     234                        protocol)
     235  --base-path BASE_PATH
    247236                        the initial portion of the request URL's "path"
     237  --http10              use HTTP/1.0 protocol instead of HTTP/1.1
     238  --http11              use HTTP/1.1 protocol (default)
    248239  -r, --auto-reload     restart automatically when sources are modified
    249   -s, --single-env      only serve a single project without the project list
    250240  -d, --daemonize       run in the background as a daemon
    251   --pidfile=PIDFILE     when daemonizing, file to which to write pid
    252   --umask=MASK          when daemonizing, file mode creation mask to use, in
    253                         octal notation (default 022)
    254   --group=GROUP         the group to run as
    255   --user=USER           the user to run as
     241  --pidfile PIDFILE     file to write pid when daemonizing
     242  --umask MASK          when daemonizing, file mode creation mask to use, in
     243                        octal notation (default: 022)
     244  --group GROUP         the group to run as
     245  --user USER           the user to run as
    256246}}}
    257247
    258248Use the -d option so that tracd doesn't hang if you close the terminal window where tracd was started.
    259249
    260 == Tips ==
    261 
    262 === Serving static content ===
    263 
    264 If `tracd` is the only web server used for the project,
    265 it can also be used to distribute static content
    266 (tarballs, Doxygen documentation, etc.)
    267 
    268 This static content should be put in the `$TRAC_ENV/htdocs` folder,
    269 and is accessed by URLs like `<project_URL>/chrome/site/...`.
    270 
    271 Example: given a `$TRAC_ENV/htdocs/software-0.1.tar.gz` file,
    272 the corresponding relative URL would be `/<project_name>/chrome/site/software-0.1.tar.gz`,
    273 which in turn can be written as `htdocs:software-0.1.tar.gz` (TracLinks syntax) or `[/<project_name>/chrome/site/software-0.1.tar.gz]` (relative link syntax).
    274 
    275  ''Support for `htdocs:` TracLinks syntax was added in version 0.10''
     250== Tips
     251
     252=== Serving static content
     253
     254If `tracd` is the only web server used for the project, it can also be used to distribute static content, such as tarballs, Doxygen documentation, etc.
     255
     256This static content should be put in the `$TRAC_ENV/htdocs` folder, and is accessed by URLs like `<project_URL>/chrome/site/...`.
     257
     258Example: given a `$TRAC_ENV/htdocs/software-0.1.tar.gz` file, the corresponding relative URL would be `/<project_name>/chrome/site/software-0.1.tar.gz`, which in turn can be written as `htdocs:software-0.1.tar.gz` (TracLinks syntax) or `[/<project_name>/chrome/site/software-0.1.tar.gz]` (relative link syntax).
    276259
    277260=== Using tracd behind a proxy
    … …  
    286269
    287270=== Authentication for tracd behind a proxy
    288 It is convenient to provide central external authentication to your tracd instances, instead of using {{{--basic-auth}}}. There is some discussion about this in #9206.
     271
     272It is convenient to provide central external authentication to your tracd instances, instead of using `--basic-auth`. See also [trac:#9206].
    289273
    290274Below is example configuration based on Apache 2.2, mod_proxy, mod_authnz_ldap.
    … …  
    292276First we bring tracd into Apache's location namespace.
    293277
    294 {{{
     278{{{#!apache
    295279<Location /project/proxified>
    296280        Require ldap-group cn=somegroup, ou=Groups,dc=domain.com
    … …  
    303287
    304288Then we need a single file plugin to recognize HTTP_REMOTE_USER header as valid authentication source. HTTP headers like '''HTTP_FOO_BAR''' will get converted to '''Foo-Bar''' during processing. Name it something like '''remote-user-auth.py''' and drop it into '''proxified/plugins''' directory:
    305 {{{
    306 #!python
     289{{{#!python
    307290from trac.core import *
    308291from trac.config import BoolOption
    … …  
    313296    implements(IAuthenticator)
    314297
    315     obey_remote_user_header = BoolOption('trac', 'obey_remote_user_header', 'false', 
    316                """Whether the 'Remote-User:' HTTP header is to be trusted for user logins 
    317                 (''since ??.??').""") 
     298    obey_remote_user_header = BoolOption('trac', 'obey_remote_user_header', 'false',
     299               """Whether the 'Remote-User:' HTTP header is to be trusted for user logins
     300                (''since ??.??').""")
    318301
    319302    def authenticate(self, req):
    320         if self.obey_remote_user_header and req.get_header('Remote-User'): 
    321             return req.get_header('Remote-User') 
     303        if self.obey_remote_user_header and req.get_header('Remote-User'):
     304            return req.get_header('Remote-User')
    322305        return None
    323306
    … …  
    325308
    326309Add this new parameter to your TracIni:
    327 {{{
    328 ...
     310{{{#!ini
    329311[trac]
    330312...
    … …  
    334316
    335317Run tracd:
    336 {{{
    337 tracd -p 8101 -r -s proxified --base-path=/project/proxified
    338 }}}
    339 
    340 Note that if you want to install this plugin for all projects, you have to put it in your [TracPlugins#Plugindiscovery global plugins_dir] and enable it in your global trac.ini.
     318{{{#!sh
     319tracd -p 8101 -s proxified --base-path=/project/proxified
     320}}}
     321
     322Note that if you want to install this plugin for all projects, you have to put it in your [TracPlugins#Plugindiscovery global plugins_directory] and enable it in your global `trac.ini`.
    341323
    342324Global config (e.g. `/srv/trac/conf/trac.ini`):
    343 {{{
     325{{{#!ini
    344326[components]
    345327remote-user-auth.* = enabled
    … …  
    351333
    352334Environment config (e.g. `/srv/trac/envs/myenv`):
    353 {{{
     335{{{#!ini
    354336[inherit]
    355337file = /srv/trac/conf/trac.ini
    356338}}}
    357339
    358 === Serving a different base path than / ===
    359 Tracd supports serving projects with different base urls than /<project>. The parameter name to change this is
    360 {{{
     340=== Serving a different base path than /
     341
     342Tracd supports serving projects with different base urls than /<project>. The parameter name to change this is:
     343{{{#!sh
    361344 $ tracd --base-path=/some/path
    362345}}}