Changes between Version 12 and Version 13 of 1.3/TracInstall
- Timestamp:
- Jul 18, 2019, 1:45:02 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
1.3/TracInstall
v12 v13 3 3 [[TranslatedPages]] 4 4 5 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://jinja.pocoo.org Jinja2] templating system, though Genshi templates will still be supported until at least Trac 1.5.1.5 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 will still be supported until at least Trac 1.5.1. 6 6 7 7 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. … … 17 17 To install Trac, the following software packages must be installed: 18 18 19 * [http ://www.python.org/ Python], version >= 2.7 and < 3.019 * [https://www.python.org/ Python], version >= 2.7 and < 3.0 20 20 (note that we dropped the support for Python 2.6 in this release) 21 21 * [https://pypi.python.org/pypi/setuptools setuptools], version >= 0.6 … … 37 37 38 38 You need to install the database and its Python bindings: 39 * [http ://www.postgresql.org/ PostgreSQL], version 9.1 or later39 * [https://www.postgresql.org/ PostgreSQL], version 9.1 or later 40 40 * [https://pypi.python.org/pypi/psycopg2 psycopg2], version 2.0 or later 41 41 … … 46 46 Trac works well with MySQL, provided you use the following: 47 47 48 * [http ://mysql.com/ MySQL], version 5.0 or later48 * [https://mysql.com/ MySQL], version 5.0 or later 49 49 * [https://pypi.python.org/pypi/PyMySQL PyMySQL] 50 50 … … 55 55 ==== Subversion 56 56 57 [http ://subversion.apache.org/ Subversion], 1.6.x or later and the '''''corresponding''''' Python bindings.58 59 There are [http ://subversion.apache.org/packages.html pre-compiled SWIG bindings] available for various platforms. See [trac:TracSubversion#GettingSubversion getting Subversion] for more information.57 [https://subversion.apache.org/ Subversion], 1.6.x or later and the '''''corresponding''''' Python bindings. 58 59 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. 60 60 61 61 {{{#!div style="border: 1pt dotted; margin: 1em" … … 69 69 ==== Git 70 70 71 [http ://git-scm.com/ Git] 1.5.6 or later is supported. More information is available on the [trac:TracGit] page.71 [https://git-scm.com/ Git] 1.5.6 or later is supported. More information is available on the [trac:TracGit] page. 72 72 73 73 ==== Other Version Control Systems … … 79 79 80 80 Alternatively you can configure Trac to run in any of the following environments: 81 * [http ://httpd.apache.org/ Apache] with81 * [https://httpd.apache.org/ Apache] with 82 82 - [https://github.com/GrahamDumpleton/mod_wsgi mod_wsgi], see [wiki:TracModWSGI] and 83 [http ://code.google.com/p/modwsgi/wiki/IntegrationWithTrac ModWSGI IntegrationWithTrac].83 [https://code.google.com/p/modwsgi/wiki/IntegrationWithTrac ModWSGI IntegrationWithTrac]. 84 84 - [http://modpython.org/ mod_python 3.5.0], see TracModPython 85 * a [http ://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi)86 * an [http ://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web85 * a [https://www.fastcgi.com/ FastCGI]-capable web server (see TracFastCgi) 86 * an [https://tomcat.apache.org/connectors-doc/ajp/ajpv13a.html AJP]-capable web 87 87 server (see [trac:TracOnWindowsIisAjp TracOnWindowsIisAjp]) 88 88 * Microsoft IIS with FastCGI and a FastCGI-to-WSGI gateway (see [trac:CookBook/Installation/TracOnWindowsIisWfastcgi IIS with FastCGI]) … … 141 141 * Install the latest development version from a tar archive: 142 142 {{{#!sh 143 $ pip install http ://download.edgewall.org/trac/Trac-latest-dev.tar.gz143 $ pip install https://download.edgewall.org/trac/Trac-latest-dev.tar.gz 144 144 }}} 145 145 * Install the unreleased 1.2-stable from subversion: … … 233 233 - //[TracCgi CGI] (should not be used, as the performance is far from optimal)// 234 234 235 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.235 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://projects.unbit.it/uwsgi/wiki/Example#Traconapacheinasub-uri uwsgi], [trac:TracOnWindowsIisIsapi Isapi-wsgi] etc. 236 236 237 237 ==== Generating the Trac cgi-bin directory #cgi-bin … … 256 256 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. 257 257 258 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.258 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. 259 259 260 260 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.