Changes between Version 22 and Version 23 of 1.1/TracInstall
- Timestamp:
- Mar 12, 2015, 6:44:52 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
1.1/TracInstall
v22 v23 9 9 If you're interested in contributing new translations for other languages or enhancing the existing translations, then please have a look at [trac:wiki:TracL10N TracL10N]. 10 10 11 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] on the main Trac site, please '''first read through these general instructions''' to get a good understanding of the tasks involved.11 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. 12 12 13 13 [[PageOutline(2-3,Installation Steps,inline)]] … … 56 56 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.) 57 57 58 Note that Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], neither does it work yet with the newer `ctype`-style bindings. 59 60 For troubleshooting information, check the [trac:TracSubversion#Troubleshooting TracSubversion] page. 61 62 '''Please note:''' if using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported]. 58 For troubleshooting information, see the [trac:TracSubversion#Troubleshooting TracSubversion] page. 59 60 {{{#!div style="border: 1pt dotted; margin: 1em" 61 **Note:** 62 * Trac '''doesn't''' use [http://pysvn.tigris.org/ PySVN], nor does it work yet with the newer `ctype`-style bindings. 63 * If using Subversion, Trac must be installed on the '''same machine'''. Remote repositories are currently [trac:ticket:493 not supported]. 64 }}} 63 65 64 66 ===== Git … … 77 79 * [http://httpd.apache.org/ Apache] with 78 80 - [http://code.google.com/p/modwsgi/ mod_wsgi], see [wiki:TracModWSGI] and 79 http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac81 [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac ModWSGI IntegrationWithTrac]. 80 82 - [http://modpython.org/ mod_python 3.5.0], (deprecated: see TracModPython) 81 83 * a [http://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi) … … 175 177 === Using installer 176 178 177 On Windows Trac can be installed using the exe installers available on the [trac:TracDownload] page. Installers are available for the 32 and 64bit versions of Python. Make sure to use the installer that matches the architecture of your Python installation.179 On Windows, Trac can be installed using the exe installers available on the [trac:TracDownload] page. Installers are available for the 32-bit and 64-bit versions of Python. Make sure to use the installer that matches the architecture of your Python installation. 178 180 179 181 === Using package manager 180 182 181 Trac may be available in the package repository for your platform. Note however, that the version provided by thepackage manager may not be the latest release.183 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. 182 184 183 185 === Advanced `easy_install` Options … … 198 200 easy_install --prefix=/usr/local --install-dir=/Library/Python/2.6/site-packages 199 201 }}} 200 Note: If installing on Mac OS X 10.6 running {{{ easy_install http://svn.edgewall.org/repos/trac/trunk }}} will install into {{{ /usr/local }}} and {{{ /Library/Python/2.6/site-packages }}} by default. 201 202 The above will place your `tracd` and `trac-admin` commands into `/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. 202 203 {{{#!div style="border: 1pt dotted; margin: 1em" 204 **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. 205 206 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. 207 }}} 203 208 204 209 == Creating a Project Environment … … 213 218 [TracAdmin trac-admin] will prompt you for the information it needs to create the environment, such as the name of the project and the [TracEnvironment#DatabaseConnectionStrings database connection string]. If you're not sure what to specify for one of these options, just press `<Enter>` to use the default value. 214 219 215 Using the default database connection string in particular will always work as long as you have SQLite installed. 216 For the other [trac:DatabaseBackend database backends] you should plan ahead and already have a database ready to use at this point. 217 218 Since 0.12, Trac doesn't ask for a [TracEnvironment#SourceCodeRepository source code repository] anymore when creating an environment. Repositories can be [TracRepositoryAdmin added] afterwards, and support for specific version control systems is disabled by default. 219 220 Also note that the values you specify here can be changed later by directly editing the [TracIni conf/trac.ini] configuration file. 220 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. 221 222 Also note that the values you specify here can be changed later using TracAdmin or directly editing the [TracIni conf/trac.ini] configuration file. 221 223 222 224 {{{#!div style="border: 1pt dotted; margin: 1em" … … 294 296 There are two primary URL paths for static resources - `/chrome/common` and `/chrome/site`. Plugins can add their own resources, usually accessible by `/chrome/<plugin>` path, so its important to override only known paths and not try to make universal `/chrome` alias for everything. 295 297 296 Note that in order to get those static resources on the filesystem, you need first to extract the relevant resources from Trac using the [TracAdmin trac-admin]` <environment>deploy` command:298 Note that in order to get those static resources on the filesystem, you need first to extract the relevant resources from Trac using the TracAdmin `deploy` command: 297 299 [[TracAdminHelp(deploy)]] 298 300 … … 327 329 }}} 328 330 329 Note that we mapped `/trac` part of the URL to the `trac.*cgi` script, and the path `/trac/chrome/common` is the path you have to append to that location to intercept requests to the static resources.331 Note that we mapped the `/trac` part of the URL to the `trac.*cgi` script, and the path `/trac/chrome/common` is the path you have to append to that location to intercept requests to the static resources. 330 332 331 333 Similarly, if you have static resources in a project's `htdocs` directory (which is referenced by `/trac/chrome/site` URL in themes), you can configure Apache to serve those resources (again, put this ''before'' the `ScriptAlias` or `WSGIScriptAlias` for the .*cgi scripts, and adjust names and locations to match your installation):