Changes between Version 3 and Version 4 of TracInstall
- Timestamp:
- 08/20/22 12:06:05 (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracInstall
v3 v4 1 = Trac Installation Guide for 1. 11 = 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].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 9 10 10 What follows 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. … … 16 16 To install Trac, the following software packages must be installed: 17 17 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 18 * [https://www.python.org/ Python], version >= 3.5 19 * [https://pypi.org/project/setuptools setuptools], version > 5.6 20 * [https://pypi.org/project/Jinja2 Jinja2], version >= 2.9.3 22 21 23 22 You also need a database system and the corresponding python bindings. The database can be either SQLite, PostgreSQL or MySQL. … … 25 24 ==== For the SQLite database #ForSQLite 26 25 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.26 You already have the SQLite database bindings bundled with the standard distribution of Python (the `sqlite3` module). 27 28 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 29 31 30 ==== For the PostgreSQL database #ForPostgreSQL 32 31 33 32 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 later33 * [https://www.postgresql.org/ PostgreSQL], version 9.1 or later 34 * [https://pypi.org/project/psycopg2 psycopg2], version 2.5 or later 36 35 37 36 See [trac:DatabaseBackend#Postgresql DatabaseBackend] for details. … … 39 38 ==== For the MySQL database #ForMySQL 40 39 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 later40 Trac works well with MySQL, provided you use the following: 41 42 * [https://mysql.com/ MySQL], version 5.0 or later 43 * [https://pypi.org/project/PyMySQL PyMySQL] 45 44 46 45 Given the caveats and known issues surrounding MySQL, read carefully the [trac:MySqlDb] page before creating the database. … … 50 49 ==== Subversion 51 50 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. 51 [https://subversion.apache.org/ Subversion], 1.14.x or later and the '''''corresponding''''' Python bindings. 52 53 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 54 58 55 {{{#!div style="border: 1pt dotted; margin: 1em" 59 56 **Note:** 60 57 * 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 * If using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are [trac:ticket:493 not supported]. 59 }}} 60 61 For troubleshooting information, see the [trac:TracSubversion#Troubleshooting TracSubversion] page. 63 62 64 63 ==== Git 65 64 66 [http ://git-scm.com/ Git] 1.5.6 or later is supported. More information is available on the [trac:TracGit] page.65 [https://git-scm.com/ Git] 1.5.6 or later is supported. More information is available on the [trac:TracGit] page. 67 66 68 67 ==== Other Version Control Systems … … 74 73 75 74 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 78 [http ://code.google.com/p/modwsgi/wiki/IntegrationWithTrac ModWSGI IntegrationWithTrac].75 * [https://httpd.apache.org/ Apache] with 76 - [https://github.com/GrahamDumpleton/mod_wsgi mod_wsgi], see [wiki:TracModWSGI] and 77 [https://code.google.com/p/modwsgi/wiki/IntegrationWithTrac ModWSGI IntegrationWithTrac]. 79 78 - [http://modpython.org/ mod_python 3.5.0], see TracModPython 80 * a [http ://www.fastcgi.com/FastCGI]-capable web server (see TracFastCgi)81 * an [http ://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web79 * a [https://fastcgi-archives.github.io FastCGI]-capable web server (see TracFastCgi) 80 * an [https://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web 82 81 server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp]) 83 82 * Microsoft IIS with FastCGI and a FastCGI-to-WSGI gateway (see [trac:CookBook/Installation/TracOnWindowsIisWfastcgi IIS with FastCGI]) 84 * a CGI-capable web server (see TracCgi), '''but usage of Trac as a cgi script 85 is highly discouraged''', better use one of the previous options. 86 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 87 86 88 87 ==== Other Python Packages 89 88 90 * [http://babel. edgewall.org Babel], version 0.9.6 or >= 1.3,89 * [http://babel.pocoo.org Babel], version >= 2.2, 91 90 needed for localization support 92 * [http://docutils.sourceforge.net/ docutils], version >= 0.3.9 93 for WikiRestructuredText. 94 * [http://pygments.org Pygments] for 95 [TracSyntaxColoring syntax highlighting]. 96 * [http://pytz.sf.net pytz] to get a complete list of time zones, 97 otherwise Trac will fall back on a shorter list from 98 an internal time zone implementation. 91 * [http://pytz.sourceforge.net pytz] to get a complete list of time zones, 92 otherwise Trac will fall back on a shorter list from 93 an internal time zone implementation. Installing Babel 94 will install pytz. 95 * [http://docutils.sourceforge.net docutils], 96 version >= 0.14, for WikiRestructuredText. 97 * [http://pygments.org Pygments], version >= 1.0, 98 for [TracSyntaxColoring syntax highlighting]. 99 * [https://pypi.org/project/textile Textile], 100 version >= 2.3, 101 for rendering the [https://github.com/textile/python-textile Textile markup language]. 102 * [https://pypi.org/project/passlib passlib] on Windows to decode [TracStandalone#BasicAuthorization:Usingahtpasswdpasswordfile htpasswd formats] other than `SHA-1`. 103 * [https://pypi.org/project/pyreadline pyreadline] on Windows for trac-admin [TracAdmin#InteractiveMode command completion]. 99 104 100 105 {{{#!div style="border: 1pt dotted; margin: 1em" … … 110 115 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. 111 116 112 === Using `easy_install`113 Trac can be installed from PyPI or the Subversion repository using [http://pypi.python.org/pypi/setuptools setuptools].114 115 A few examples:116 117 - Install the latest stable version of Trac:118 {{{#!sh119 $ easy_install Trac120 }}}121 - Install latest development version:122 {{{#!sh123 $ easy_install http://download.edgewall.org/trac/Trac-latest-dev.tar.gz124 }}}125 Note that in this case you won't have the possibility to run a localized version of Trac;126 either use a released version or install from source127 128 More information can be found on the [trac:wiki:setuptools setuptools] page.129 130 {{{#!div style="border: 1pt dotted; margin: 1em"131 **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].132 }}}133 134 117 === Using `pip` 135 'pip' is an easy_install replacement that is very useful to quickly install python packages. 136 To get a Trac installation up and running in less than 5 minutes: 137 138 Assuming you want to have your entire pip installation in `/opt/user/trac` 139 140 - 141 {{{#!sh 142 pip install trac psycopg2 143 }}} 144 or 145 - 146 {{{#!sh 147 pip install trac mysql-python 148 }}} 149 150 Make sure your OS specific headers are available for pip to automatically build PostgreSQL (`libpq-dev`) or MySQL (`libmysqlclient-dev`) bindings. 151 152 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`. 153 154 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) 155 156 Additionally, you can install several Trac plugins (listed [https://pypi.python.org/pypi?:action=browse&show=all&c=516 here]) through pip. 157 158 === From source 159 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. 160 161 {{{#!sh 162 $ python ./setup.py install 163 }}} 164 165 ''You will need root permissions or equivalent for this step.'' 166 167 This will byte-compile the Python source code and install it as an .egg file or folder in the `site-packages` directory 168 of your Python installation. The .egg will also contain all other resources needed by standard Trac, such as `htdocs` and `templates`. 169 170 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): 171 {{{#!sh 172 $ python ./setup.py install 173 }}} 174 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`). 118 `pip` is the modern Python package manager and is included in Python distributions. `pip` will automatically 119 resolve the //required// dependencies (Jinja2 and 120 setuptools) and download the latest packages from pypi.org. 121 122 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: 123 124 {{{#!sh 125 $ pip install . 126 }}} 127 128 `pip` supports numerous other install mechanisms. It can be passed the URL of an archive or other download location. Here are some examples: 129 130 * Install the latest stable version from a zip archive: 131 {{{#!sh 132 $ pip install https://download.edgewall.org/trac/Trac-latest.zip 133 }}} 134 * Install the latest development version from a tar archive: 135 {{{#!sh 136 $ pip install https://download.edgewall.org/trac/Trac-latest-dev.tar.gz 137 }}} 138 * Install the unreleased 1.4-stable from subversion: 139 {{{#!sh 140 $ pip install svn+https://svn.edgewall.org/repos/trac/branches/1.2-stable 141 }}} 142 * Install the latest development preview (//not recommended for production installs//): 143 {{{#!sh 144 $ pip install --find-links=https://trac.edgewall.org/wiki/TracDownload Trac 145 }}} 146 147 The optional dependencies can be installed from PyPI using `pip`: 148 {{{#!sh 149 $ pip install babel docutils pygments textile 150 }}} 151 152 The optional dependencies can alternatively be 153 specified using the `extras` keys in the setup file: 154 {{{#!sh 155 $ pip install Trac[babel,rest,pygments,textile] 156 }}} 157 158 `rest` is the extra that installs the `docutils` 159 dependency. 160 161 Include `mysql` or `psycopg2-binary` in the 162 list if using the MySQL or PostgreSQL database. 163 164 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. 175 165 176 166 === Using installer … … 180 170 === Using package manager 181 171 182 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. 183 184 === Advanced `easy_install` Options 185 186 To install Trac to a custom location, or find out about other advanced installation options, run: 187 {{{#!sh 188 easy_install --help 189 }}} 190 191 Also see [http://docs.python.org/2/install/index.html Installing Python Modules] for detailed information. 192 193 Specifically, you might be interested in: 194 {{{#!sh 195 easy_install --prefix=/path/to/installdir 196 }}} 197 or, if installing Trac on a Mac OS X system: 198 {{{#!sh 199 easy_install --prefix=/usr/local --install-dir=/Library/Python/2.6/site-packages 200 }}} 201 202 {{{#!div style="border: 1pt dotted; margin: 1em" 203 **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. 204 205 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. 206 }}} 172 Trac may be available in your platform's package repository. However, your package manager may not provide the latest release of Trac. 207 173 208 174 == Creating a Project Environment … … 215 181 }}} 216 182 217 [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. 183 [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. 218 184 219 185 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. 220 186 221 187 Also note that the values you specify here can be changed later using TracAdmin or directly editing the [TracIni conf/trac.ini] configuration file. 222 223 {{{#!div style="border: 1pt dotted; margin: 1em"224 **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.225 }}}226 188 227 189 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: … … 238 200 == Deploying Trac 239 201 240 {{{#!div style="border: 1pt dotted; margin: 1em"241 **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.242 243 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.244 245 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`.246 {{{#!sh247 export PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1248 }}}249 250 Alternatively, the variable can be set in the shell before executing `tracd`:251 {{{#!sh252 $ PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject253 }}}254 255 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`.256 }}}257 258 202 === Running the Standalone Server 259 203 … … 263 207 }}} 264 208 265 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:209 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: 266 210 {{{#!sh 267 211 $ tracd -s --port 8000 /path/to/myproject … … 270 214 === Running Trac on a Web Server 271 215 272 Trac provides various options for connecting to a "real" web server: 216 Trac provides various options for connecting to a "real" web server: 273 217 - [TracFastCgi FastCGI] 274 - [wiki:TracModWSGI Apache with mod_wsgi] 218 - [wiki:TracModWSGI Apache with mod_wsgi] 275 219 - [TracModPython Apache with mod_python] 276 - //[TracCgi CGI](should not be used, as the performance is far from optimal)//277 278 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.220 - [TracCgi CGI] //(should not be used, as the performance is far from optimal)// 221 222 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. 279 223 280 224 ==== Generating the Trac cgi-bin directory #cgi-bin 281 225 282 In order for Trac to function properly with FastCGI you need to have a `trac.fcgi` file and for mod_wsgi a `trac.wsgi` file. These are Python scripts which load the appropriate Python code. They can be generated using the `deploy` option of [TracAdmin trac-admin]. 283 284 There is, however, a bit of a chicken-and-egg problem. The [TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this: 285 {{{#!sh 286 mkdir -p /usr/share/trac/projects/my-project 287 trac-admin /usr/share/trac/projects/my-project initenv 288 trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy 289 mv /tmp/deploy/* /usr/share/trac 290 }}} 291 Don't forget to check that the web server has the execution right on scripts in the `/usr/share/trac/cgi-bin` directory. 226 Application scripts for CGI, FastCGI and mod-wsgi can be generated using the [TracAdmin trac-admin] `deploy` command: 227 [[TracAdminHelp(deploy)]] 228 229 Grant the web server execution right on scripts in the `cgi-bin` directory. 230 231 For example, the following yields a typical directory structure: 232 {{{#!sh 233 $ mkdir -p /var/trac 234 $ trac-admin /var/trac/<project> initenv 235 $ trac-admin /var/trac/<project> deploy /var/www 236 $ ls /var/www 237 cgi-bin htdocs 238 $ chmod ugo+x /var/www/cgi-bin/* 239 }}} 292 240 293 241 ==== Mapping Static Resources … … 295 243 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. 296 244 297 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.245 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. 298 246 299 247 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. 300 248 301 A single `/chrome` alias can used if the static resources are extracted for all plugins. This means that the `deploy` command must be executed after installing or updating a plugin that provides static resources, or after modifying resources in the `$env/htdocs` directory. This is probably appropriate for most installations but may not be what you want if, for example, you wish to upload plugins through the //Plugins// administration page. 302 303 The resources are extracted using the [TracAdmin trac-admin]` <environment> deploy` command: 304 [[TracAdminHelp(deploy)]] 305 306 The target `<directory>` will contain an `htdocs` directory with: 249 A single `/chrome` alias can used if the static resources are extracted for all plugins. This means that the `deploy` command (discussed in the previous section) must be executed after installing or updating a plugin that provides static resources, or after modifying resources in the `$env/htdocs` directory. This is probably appropriate for most installations but may not be what you want if, for example, you wish to upload plugins through the //Plugins// administration page. 250 251 The `deploy` command creates an `htdocs` directory with: 307 252 - `common/` - the static resources of Trac 308 253 - `site/` - a copy of the environment's `htdocs/` directory … … 322 267 Assuming the deployment has been done this way: 323 268 {{{#!sh 324 $ trac-admin /var/trac/ env deploy /path/to/shared/trac269 $ trac-admin /var/trac/<project> deploy /var/www 325 270 }}} 326 271 … … 366 311 }}} 367 312 368 Another alternative to aliasing `/trac/chrome/common` is having Trac generate direct links for those static resources (and only those), using the [ [TracIni#trac-section| [trac] htdocs_location]] configuration setting:313 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: 369 314 {{{#!ini 370 315 [trac] … … 387 332 Trac uses HTTP authentication. You'll need to configure your webserver 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 333 389 The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. 334 The process of adding, removing, and configuring user accounts for authentication depends on the specific way you run Trac. 390 335 391 336 Please refer to one of the following sections: … … 406 351 == Configuring Trac 407 352 353 Configuration options are documented on the TracIni page. 354 408 355 TracRepositoryAdmin provides information on configuring version control repositories for your project. 409 356 357 In addition to the optional version control backends, Trac provides several optional features that are disabled by default: 358 * [TracFineGrainedPermissions#AuthzPolicy Fine-grained permission policy] 359 * [TracPermissions#CreatingNewPrivileges Custom permissions] 360 * [TracTickets#deleter Ticket deletion] 361 * [TracTickets#cloner Ticket cloning] 362 * [TracRepositoryAdmin#CommitTicketUpdater Ticket changeset references] 363 410 364 == Using Trac 411 365 … … 419 373 420 374 ---- 421 See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracUpgrade , TracPermissions375 See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracUpgrade