Changes between Version 4 and Version 5 of TracInstall
- Timestamp:
- Sep 24, 2024, 8:59:24 AM (5 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracInstall
v4 v5 1 = Trac Installation Guide for 1. 21 = Trac Installation Guide for 1.5 2 2 [[TracGuideToc]] 3 3 4 Trac is written in the Python programming language and needs a database, [http ://sqlite.org/ SQLite], [http://www.postgresql.org/ PostgreSQL], or [http://mysql.com/ MySQL]. For HTML rendering, Trac uses the [http://genshi.edgewall.org Genshi] templating system.4 Trac is written in the Python programming language and needs a database, [https://sqlite.org/ SQLite], [https://www.postgresql.org/ PostgreSQL], or [https://mysql.com/ MySQL]. For HTML rendering, Trac uses the [http://jinja.pocoo.org Jinja2] templating system, though Genshi templates are supported until Trac 1.5.1. 5 5 6 6 Trac can also be localized, and there is probably a translation available in your language. If you want to use the Trac interface in other languages, then make sure you have installed the optional package [#OtherPythonPackages Babel]. Pay attention to the extra steps for localization support in the [#InstallingTrac Installing Trac] section below. Lacking Babel, you will only get the default English version. 7 7 8 If you're interested in contributing new translations for other languages or enhancing the existing translations, thenplease have a look at [trac:wiki:TracL10N TracL10N].9 10 What followsare generic instructions for installing and setting up Trac. While you may find instructions for installing Trac on specific systems at [trac:TracInstallPlatforms TracInstallPlatforms], please '''first read through these general instructions''' to get a good understanding of the tasks involved.8 If you're interested in contributing new translations for other languages or enhancing the existing translations, please have a look at [trac:wiki:TracL10N TracL10N]. 9 10 These are generic instructions for installing and setting up Trac. While you may find instructions for installing Trac on specific systems at [trac:TracInstallPlatforms TracInstallPlatforms], please '''first read through these general instructions''' to get a good understanding of the tasks involved. 11 11 12 12 [[PageOutline(2-3,Installation Steps,inline)]] … … 14 14 == Dependencies 15 15 === Mandatory Dependencies 16 16 17 To install Trac, the following software packages must be installed: 17 18 18 * [http://www.python.org/ Python], version >= 2.6 and < 3.0 19 (note that we dropped the support for Python 2.5 in this release) 20 * [http://pypi.python.org/pypi/setuptools setuptools], version >= 0.6 21 * [http://genshi.edgewall.org/wiki/Download Genshi], version >= 0.6 22 23 You also need a database system and the corresponding python bindings. The database can be either SQLite, PostgreSQL or MySQL. 19 * [https://www.python.org/ Python], version >= 3.5 20 * [https://pypi.org/project/setuptools setuptools], version > 5.6 21 * [https://pypi.org/project/Jinja2 Jinja2], version >= 2.9.3 22 23 You also need a database system and the corresponding Python bindings. The database can be either SQLite, PostgreSQL or MySQL. 24 24 25 25 ==== For the SQLite database #ForSQLite 26 26 27 As you must be using Python 2.6 or 2.7, you already have the SQLite database bindings bundled with the standard distribution of Python (the `sqlite3` module).28 29 Optionally, you may install a newer version of [http ://pypi.python.org/pypi/pysqlite pysqlite] than the one provided by the Python distribution. See [trac:PySqlite#ThePysqlite2bindings PySqlite] for details.27 You already have the SQLite database bindings bundled with the standard distribution of Python (the `sqlite3` module). 28 29 Optionally, you may install a newer version of [https://pypi.org/project/pysqlite pysqlite] than the one provided by the Python distribution. See [trac:PySqlite#ThePysqlite2bindings PySqlite] for details. 30 30 31 31 ==== For the PostgreSQL database #ForPostgreSQL 32 32 33 33 You need to install the database and its Python bindings: 34 * [http ://www.postgresql.org/ PostgreSQL], version 8.0or later35 * [http ://pypi.python.org/pypi/psycopg2 psycopg2], version 2.0or later34 * [https://www.postgresql.org/ PostgreSQL], version 9.1 or later 35 * [https://pypi.org/project/psycopg2 psycopg2], version 2.5 or later 36 36 37 37 See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details. … … 39 39 ==== For the MySQL database #ForMySQL 40 40 41 Trac works well with MySQL, provided you follow the guidelines:42 43 * [http ://mysql.com/ MySQL], version 5.0 or later44 * [http ://sf.net/projects/mysql-python MySQLdb], version 1.2.2 or later41 Trac works well with MySQL, provided you use the following: 42 43 * [https://mysql.com/ MySQL], version 5.0 or later 44 * [https://pypi.org/project/PyMySQL PyMySQL] 45 45 46 46 Given the caveats and known issues surrounding MySQL, read carefully the [trac:MySqlDb] page before creating the database. … … 50 50 ==== Subversion 51 51 52 [http://subversion.apache.org/ Subversion], 1.6.x or later and the '''''corresponding''''' Python bindings. 53 54 There are [http://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. (Good luck finding precompiled SWIG bindings for any Windows package at that listing. [trac:TracSubversion] points you to [http://alagazam.net Alagazam], which works for me under Python 2.6.) 55 56 For troubleshooting information, see the [trac:TracSubversion#Troubleshooting TracSubversion] page. 52 [https://subversion.apache.org/ Subversion], 1.14.x or later and the '''corresponding''' Python bindings. 53 54 There are [https://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. See [trac:TracSubversion#GettingSubversion getting Subversion] for more information. 57 55 58 56 {{{#!div style="border: 1pt dotted; margin: 1em" 59 57 **Note:** 60 * Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], nor does it work yet with the newer `ctype`-style bindings. 61 * If using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported]. 62 }}} 58 * Trac '''doesn't''' use [https://pypi.org/project/PySVN PySVN], nor does it work yet with the newer `ctype`-style bindings. 59 * If using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are [trac:ticket:493 not supported]. 60 }}} 61 62 For troubleshooting information, see the [trac:TracSubversion#Troubleshooting TracSubversion] page. 63 63 64 64 ==== Git 65 65 66 [http ://git-scm.com/ Git] 1.5.6 or later is supported. More information is available on the [trac:TracGit] page.66 [https://git-scm.com/ Git] 1.5.6 or later is supported. More information is available on the [trac:TracGit] page. 67 67 68 68 ==== Other Version Control Systems … … 71 71 72 72 ==== Web Server 73 73 74 A web server is optional because Trac is shipped with a server included, see the [#RunningtheStandaloneServer Running the Standalone Server] section below. 74 75 75 76 Alternatively you can configure Trac to run in any of the following environments: 76 * [http ://httpd.apache.org/ Apache] with77 * [https://github.com/GrahamDumpleton/mod_wsgi mod_wsgi], see [wiki:TracModWSGI] and [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac ModWSGI IntegrationWithTrac].78 * [http://modpython.org/ mod_python 3.5.0], see TracModPython79 * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi)80 * a n [http://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web81 77 * [https://httpd.apache.org/ Apache] with 78 - [https://github.com/GrahamDumpleton/mod_wsgi mod_wsgi], see [wiki:TracModWSGI] and 79 [https://code.google.com/p/modwsgi/wiki/IntegrationWithTrac ModWSGI IntegrationWithTrac]. 80 - [http://modpython.org/ mod_python 3.5.0], see TracModPython 81 * a [https://fastcgi-archives.github.io FastCGI]-capable web server (see TracFastCgi) 82 * an [https://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp]) 82 83 * Microsoft IIS with FastCGI and a FastCGI-to-WSGI gateway (see [trac:CookBook/Installation/TracOnWindowsIisWfastcgi IIS with FastCGI]) 83 * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script 84 is highly discouraged''', better use one of the previous options. 85 84 * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script is highly discouraged''', better use one of the previous options. 86 85 87 86 ==== Other Python Packages 88 87 89 * [http://babel.edgewall.org Babel], version 0.9.6 or >= 1.3, 90 needed for localization support 91 * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9 92 for WikiRestructuredText. 93 * [http://pygments.org Pygments] for 94 [TracSyntaxColoring syntax highlighting]. 95 * [http://pytz.sf.net pytz] to get a complete list of time zones, 96 otherwise Trac will fall back on a shorter list from 97 an internal time zone implementation. 88 * [http://babel.pocoo.org Babel], version >= 2.2, needed for localization support 89 * [http://pytz.sourceforge.net pytz] to get a complete list of time zones, otherwise Trac will fall back on a shorter list from an internal time zone implementation. Installing Babel will install pytz. 90 * [http://docutils.sourceforge.net docutils], version >= 0.14, for WikiRestructuredText. 91 * [http://pygments.org Pygments], version >= 1.0, for [TracSyntaxColoring syntax highlighting]. 92 * [https://pypi.org/project/textile Textile], version >= 2.3, for rendering the [https://github.com/textile/python-textile Textile markup language]. 93 * [https://pypi.org/project/passlib passlib] on Windows to decode [TracStandalone#BasicAuthorization:Usingahtpasswdpasswordfile htpasswd formats] other than `SHA-1`. 94 * [https://pypi.org/project/pyreadline pyreadline] on Windows for trac-admin [TracAdmin#InteractiveMode command completion]. 98 95 99 96 {{{#!div style="border: 1pt dotted; margin: 1em" … … 109 106 It is assumed throughout this guide that you have elevated permissions as the `root` user or by prefixing commands with `sudo`. The umask `0002` should be used for a typical installation on a Unix-based platform. 110 107 111 === Using `easy_install`112 Trac can be installed from PyPI or the Subversion repository using [http://pypi.python.org/pypi/setuptools setuptools].113 114 A few examples:115 116 - Install the latest stable version of Trac:117 {{{#!sh118 $ easy_install Trac119 }}}120 - Install latest development version:121 {{{#!sh122 $ easy_install http://download.edgewall.org/trac/Trac-latest-dev.tar.gz123 }}}124 Note that in this case you won't have the possibility to run a localized version of Trac;125 either use a released version or install from source126 127 More information can be found on the [trac:wiki:setuptools setuptools] page.128 129 {{{#!div style="border: 1pt dotted; margin: 1em"130 **Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation. More information may be found in [#DeployingTrac Deploying Trac].131 }}}132 133 108 === Using `pip` 134 'pip' is an easy_install replacement that is very useful to quickly install python packages. 135 To get a Trac installation up and running in less than 5 minutes: 136 137 Assuming you want to have your entire pip installation in `/opt/user/trac` 138 139 {{{#!sh 140 $ pip install trac psycopg2 141 }}} 142 or 143 {{{#!sh 144 $ pip install trac mysql-python 145 }}} 146 147 Make sure your OS specific headers are available for pip to automatically build PostgreSQL (`libpq-dev`) or MySQL (`libmysqlclient-dev`) bindings. 148 149 pip will automatically resolve all dependencies (like Genshi, pygments, etc.), download the latest packages from pypi.python.org and create a self contained installation in `/opt/user/trac`. 150 151 All commands (`tracd`, `trac-admin`) are available in `/opt/user/trac/bin`. This can also be leveraged for `mod_python` (using `PythonHandler` directive) and `mod_wsgi` (using `WSGIDaemonProcess` directive) 152 153 Additionally, you can install several Trac plugins (listed [https://pypi.python.org/pypi?:action=browse&show=all&c=516 here]) through pip. 154 155 === From source 156 Using the python-typical setup at the top of the source directory also works. You can obtain the source for a .tar.gz or .zip file corresponding to a release (e.g. `Trac-1.0.tar.gz`) from the [trac:TracDownload] page, or you can get the source directly from the repository. See [trac:TracRepositories#OfficialSubversionrepository TracRepositories] for details. 157 158 {{{#!sh 159 $ python ./setup.py install 160 }}} 161 162 ''You will need root permissions or equivalent for this step.'' 163 164 This will byte-compile the Python source code and install it as an .egg file or folder in the `site-packages` directory 165 of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as `htdocs` and `templates`. 166 167 If you install from source and want to make Trac available in other languages, make sure Babel is installed. Only then, perform the `install` (or simply redo the `install` once again afterwards if you realize Babel was not yet installed): 168 {{{#!sh 169 $ python ./setup.py install 170 }}} 171 Alternatively, you can run `bdist_egg` and copy the .egg from `dist/` to the place of your choice, or you can create a Windows installer (`bdist_wininst`). 109 110 `pip` is the modern Python package manager and is included in Python distributions. `pip` will automatically resolve the //required// dependencies (Jinja2 and setuptools) and download the latest packages from pypi.org. 111 112 You can also install directly from a source package. You can obtain the source in a tar or zip from the [trac:TracDownload] page. After extracting the archive, change to the directory containing `setup.py` and run: 113 114 {{{#!sh 115 $ pip install . 116 }}} 117 118 `pip` supports numerous other install mechanisms. It can be passed the URL of an archive or other download location. Here are some examples: 119 120 * Install the latest development version from a tar archive: 121 {{{#!sh 122 $ pip install https://download.edgewall.org/trac/Trac-latest-dev.tar.gz 123 }}} 124 * Install the unreleased 1.4-stable from subversion: 125 {{{#!sh 126 $ pip install svn+https://svn.edgewall.org/repos/trac/branches/1.4-stable 127 }}} 128 * Install the latest development preview (//not recommended for production installs//): 129 {{{#!sh 130 $ pip install --find-links=https://trac.edgewall.org/wiki/TracDownload Trac 131 }}} 132 133 The optional dependencies can be installed from PyPI using `pip`: 134 {{{#!sh 135 $ pip install babel docutils pygments textile 136 }}} 137 138 The optional dependencies can alternatively be 139 specified using the `extras` keys in the setup file: 140 {{{#!sh 141 $ pip install Trac[babel,rest,pygments,textile] 142 }}} 143 144 `rest` is the extra that installs the `docutils` 145 dependency. 146 147 Include `mysql` or `psycopg2-binary` in the 148 list if using the MySQL or PostgreSQL database. 149 150 Additionally, you can install several Trac plugins from PyPI (listed [https://pypi.org/search/?c=Framework+%3A%3A+Trac here]) using pip. See TracPlugins for more information. 172 151 173 152 === Using installer … … 177 156 === Using package manager 178 157 179 Trac may be available in your platform's package repository. Note however, that the version provided by your package manager may not be the latest release. 180 181 === Advanced `easy_install` Options 182 183 To install Trac to a custom location, or find out about other advanced installation options, run: 184 {{{#!sh 185 $ easy_install --help 186 }}} 187 188 Also see [http://docs.python.org/2/install/index.html Installing Python Modules] for detailed information. 189 190 Specifically, you might be interested in: 191 {{{#!sh 192 $ easy_install --prefix=/path/to/installdir 193 }}} 194 or, if installing Trac on a Mac OS X system: 195 {{{#!sh 196 $ easy_install --prefix=/usr/local --install-dir=/Library/Python/2.6/site-packages 197 }}} 198 199 {{{#!div style="border: 1pt dotted; margin: 1em" 200 **Mac OS X Note:** On Mac OS X 10.6, running `easy_install trac` will install into `/usr/local` and `/Library/Python/2.6/site-packages` by default. 201 202 The `tracd` and `trac-admin` commands will be placed in `/usr/local/bin` and will install the Trac libraries and dependencies into `/Library/Python/2.6/site-packages`, which is Apple's preferred location for third-party Python application installations. 203 }}} 158 Trac may be available in your platform's package repository. However, your package manager may not provide the latest release of Trac. 204 159 205 160 == Creating a Project Environment … … 212 167 }}} 213 168 214 You will be prompted for the information needed to create the environment: the name of the project and the [TracEnvironment#DatabaseConnectionStrings database connection string]. If you're not sure what to specify for any of these options, just press `<Enter>` to use the default value. 169 [TracAdmin trac-admin] will prompt you for the information it needs to create the environment: the name of the project and the [TracEnvironment#DatabaseConnectionStrings database connection string]. If you're not sure what to specify for any of these options, just press `<Enter>` to use the default value. 215 170 216 171 Using the default database connection string will always work as long as you have SQLite installed. For the other [trac:DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point. 217 172 218 173 Also note that the values you specify here can be changed later using TracAdmin or directly editing the [TracIni conf/trac.ini] configuration file. 219 220 {{{#!div style="border: 1pt dotted; margin: 1em"221 **Filesystem Warning:** When selecting the location of your environment, make sure that the filesystem on which the environment directory resides supports sub-second timestamps (i.e. **not** `ext2` or `ext3` on Linux, or HFS+ on OSX), as the modification time of the `conf/trac.ini` file will be monitored to decide whether an environment restart is needed or not. A too coarse-grained timestamp resolution may result in inconsistencies in Trac < 1.0.2. The best advice is to opt for a platform with sub-second timestamp resolution, regardless of the Trac version.222 }}}223 174 224 175 Finally, make sure the user account under which the web front-end runs will have '''write permissions''' to the environment directory and all the files inside. This will be the case if you run `trac-admin ... initenv` as this user. If not, you should set the correct user afterwards. For example on Linux, with the web server running as user `apache` and group `apache`, enter: … … 235 186 == Deploying Trac 236 187 237 {{{#!div style="border: 1pt dotted; margin: 1em"238 **Setuptools Warning:** If the version of your setuptools is in the range 5.4 through 5.6, the environment variable `PKG_RESOURCES_CACHE_ZIP_MANIFESTS` must be set in order to avoid significant performance degradation.239 240 If running `tracd`, the environment variable can be set system-wide or for just the user that runs the `tracd` process. There are several ways to accomplish this in addition to what is discussed here, and depending on the distribution of your OS.241 242 To be effective system-wide a shell script with the `export` statement may be added to `/etc/profile.d`. To be effective for a user session the `export` statement may be added to `~/.profile`.243 {{{#!sh244 export PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1245 }}}246 247 Alternatively, the variable can be set in the shell before executing `tracd`:248 {{{#!sh249 $ PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject250 }}}251 252 If running the Apache web server, !Ubuntu/Debian users should add the `export` statement to `/etc/apache2/envvars`. !RedHat/CentOS/Fedora should can add the `export` statement to `/etc/sysconfig/httpd`.253 }}}254 255 188 === Running the Standalone Server 256 189 … … 260 193 }}} 261 194 262 Then, fire upa browser and visit `http://localhost:8000/`. You should get a simple listing of all environments that `tracd` knows about. Follow the link to the environment you just created, and you should see Trac in action. If you only plan on managing a single project with Trac you can have the standalone server skip the environment list by starting it like this:195 Then, open a browser and visit `http://localhost:8000/`. You should get a simple listing of all environments that `tracd` knows about. Follow the link to the environment you just created, and you should see Trac in action. If you only plan on managing a single project with Trac you can have the standalone server skip the environment list by starting it like this: 263 196 {{{#!sh 264 197 $ tracd -s --port 8000 /path/to/myproject … … 267 200 === Running Trac on a Web Server 268 201 269 Trac provides various options for connecting to a "real" web server: 202 Trac provides various options for connecting to a "real" web server: 270 203 - [TracFastCgi FastCGI] 271 - [wiki:TracModWSGI Apache with mod_wsgi] 204 - [wiki:TracModWSGI Apache with mod_wsgi] 272 205 - [TracModPython Apache with mod_python] 273 206 - [TracCgi CGI] //(should not be used, as the performance is far from optimal)// 274 207 275 Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. Other deployment scenarios are possible: [trac:TracNginxRecipe nginx], [http ://projects.unbit.it/uwsgi/wiki/Example#Traconapacheinasub-uri uwsgi], [trac:TracOnWindowsIisIsapi Isapi-wsgi] etc.208 Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS. Other deployment scenarios are possible: [trac:TracNginxRecipe nginx], [https://uwsgi-docs.readthedocs.io/en/latest/#Traconapacheinasub-uri uwsgi], [trac:TracOnWindowsIisIsapi Isapi-wsgi] etc. 276 209 277 210 ==== Generating the Trac cgi-bin directory #cgi-bin … … 296 229 Without additional configuration, Trac will handle requests for static resources such as stylesheets and images. For anything other than a TracStandalone deployment, this is not optimal as the web server can be set up to directly serve the static resources. For CGI setup, this is '''highly undesirable''' as it causes abysmal performance. 297 230 298 Web servers such as [http ://httpd.apache.org/ Apache] allow you to create //Aliases// to resources, giving them a virtual URL that doesn't necessarily reflect their location on the file system. We can map requests for static resources directly to directories on the file system, to avoid Trac processing the requests.231 Web servers such as [https://httpd.apache.org/ Apache] allow you to create //Aliases// to resources, giving them a virtual URL that doesn't necessarily reflect their location on the file system. We can map requests for static resources directly to directories on the file system, to avoid Trac processing the requests. 299 232 300 233 There are two primary URL paths for static resources: `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible at the `/chrome/<plugin>` path. … … 320 253 Assuming the deployment has been done this way: 321 254 {{{#!sh 322 $ trac-admin /var/trac/<project> deploy /var/www 255 $ trac-admin /var/trac/<project> deploy /var/www/trac 323 256 }}} 324 257 325 258 Add the following snippet to Apache configuration, changing paths to match your deployment. The snippet must be placed ''before'' the `ScriptAlias` or `WSGIScriptAlias` directive, because those directives map all requests to the Trac application: 326 259 {{{#!apache 327 Alias /trac/chrome / path/to/trac/htdocs328 329 <Directory "/ path/to/www/trac/htdocs">260 Alias /trac/chrome /var/www/trac/htdocs 261 262 <Directory "/var/www/trac/htdocs"> 330 263 # For Apache 2.2 331 264 <IfModule !mod_authz_core.c> … … 364 297 }}} 365 298 366 Another alternative to aliasing `/trac/chrome/common` is having Trac generate direct links for those static resources (and only those), using the [TracIni#trac- sectionhtdocs_location] configuration setting:299 Another alternative to aliasing `/trac/chrome/common` is having Trac generate direct links for those static resources (and only those), using the [TracIni#trac-htdocs_location-option trac.htdocs_location] configuration setting: 367 300 {{{#!ini 368 301 [trac] … … 377 310 }}} 378 311 379 ==== Setting up the Plugin Cache #egg-cache312 ==== Setting up the Plugin Cache 380 313 381 314 Some Python plugins need to be extracted to a cache directory. By default the cache resides in the home directory of the current user. When running Trac on a Web Server as a dedicated user (which is highly recommended) who has no home directory, this might prevent the plugins from starting. To override the cache location you can set the `PYTHON_EGG_CACHE` environment variable. Refer to your server documentation for detailed instructions on how to set environment variables. 382 315 383 If you setup hook scripts that call Trac, such as the Subversion post-commit hook script provided in the `/contrib` directory, make sure you define the `PYTHON_EGG_CACHE` environment variable within these scripts as well.384 385 316 == Configuring Authentication 386 317 387 Trac uses HTTP authentication. You'll need to configure your web server to request authentication when the `.../login` URL is hit (the virtual path of the "login" button). Trac will automatically pick the `REMOTE_USER` variable up after you provide your credentials. Therefore, all user management goes through your web server configuration. Please consult the documentation of your web server for more info.388 389 The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. 318 Trac uses HTTP authentication. You'll need to configure your web server to request authentication when the `.../login` URL is hit (the virtual path of the "login" button). Trac will automatically pick the `REMOTE_USER` variable up after you provide your credentials. Therefore, all user management goes through your web server configuration. Please consult the documentation of your web server for more info. 319 320 The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. 390 321 391 322 Please refer to one of the following sections: … … 406 337 == Configuring Trac 407 338 339 Configuration options are documented on the TracIni page. 340 408 341 TracRepositoryAdmin provides information on configuring version control repositories for your project. 409 342 343 In addition to the optional version control backends, Trac provides several optional features that are disabled by default: 344 * [TracFineGrainedPermissions#AuthzPolicy Fine-grained permission policy] 345 * [TracPermissions#CreatingNewPrivileges Custom permissions] 346 * [TracTickets#deleter Ticket deletion] 347 * [TracTickets#cloner Ticket cloning] 348 * [TracRepositoryAdmin#CommitTicketUpdater Ticket changeset references] 349 410 350 == Using Trac 411 351 … … 419 359 420 360 ---- 421 See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracUpgrade , TracPermissions361 See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracUpgrade