Edgewall Software

Changes between Version 9 and Version 10 of 0.12/TracInstall


Ignore:
Timestamp:
Nov 23, 2009, 8:00:05 PM (13 years ago)
Author:
Christian Boos
Comment:

sync with [8848]

Legend:

Unmodified
Added
Removed
Modified
  • 0.12/TracInstall

    v9 v10  
    33#!div style="margin-top: .5em; padding: 0 1em; background-color: #ffd; border:1px outset #ddc;"
    44
    5   '''NOTE: this page is for 0.12dev (trunk), for which development has started. For installing previous Trac versions, please refer to TracInstall (0.11)'''
     5  '''NOTE: this page is for 0.12dev (trunk), the version currently in development. For installing previous Trac versions, please refer to TracInstall (0.11)'''
    66}}}
    77[[TracGuideToc]]
     
    2828=== For SQLite ===
    2929
    30 If you're using Python 2.5 or newer, you'll have a bundled version of SQLite and the bindings. If you're using Python 2.4 or you want to use a specific version of SQLite and/or the bindings, you can grab them from:
    31  * [http://www.sqlite.org/ sqlite.org]
    32  * [http://pysqlite.org/ pysqlite.org]
    33 
    34 Note that SQLite v2.x databases are not supported anymore, you
    35 need to migrate them to SQLite v3.x.
    36 
    37 For details see the [trac:PySqlite PySqlite] page.
    38 
     30If you're using Python 2.5 or 2.6, you already have everything you need.
     31
     32If you're using Python 2.4 and need pysqlite, you can download from
     33[http://code.google.com/p/pysqlite/downloads/list google code] the Windows
     34installers or the tar.gz archive for building from source:
     35{{{
     36$ tar xvfz <version>.tar.gz
     37$ cd <version>
     38$ python setup.py build_static install
     39}}}
     40 
     41That way, the latest SQLite version will be downloaded and built into the
     42bindings.
     43
     44SQLite 2.x is no longer supported. For SQLite 3.x, the pysqlite 1.1.x
     45bindings are also no longer supported, use pysqlite 2.x.
     46
     47See additional information in [trac:PySqlite PySqlite].
    3948
    4049=== For PostgreSQL ===
     
    4958=== For MySQL ===
    5059
    51 MySQL support is now good in Trac, provided you follow the guidelines.
     60Trac can now work quite well with MySQL, provided you follow the guidelines.
    5261
    5362 * [http://mysql.com/ MySQL], version 5.0 or later
     
    5564
    5665See [trac:MySqlDb MySqlDb] for more detailed information.
    57 
     66It is ''very'' important to read carefully that page before creating the database.
    5867
    5968=== Optional Requirements ===
     
    174183  chown -R apache.apache /path/to/myproject
    175184
    176 
    177185== Running the Standalone Server ==
    178186
     
    187195}}}
    188196
    189 
    190197== Running Trac on a Web Server ==
    191198
    192 Trac provides three options for connecting to a "real" web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI], [wiki:TracModPython mod_python], [wiki:TracModWSGI mod_wsgi]. For decent performance, it is recommended that you use either FastCGI, mod_python or mod_wsgi.
    193 
     199Trac provides three options for connecting to a "real" web server: [wiki:TracCgi CGI], [wiki:TracFastCgi FastCGI] and [wiki:TracModPython mod_python]. For decent performance, it is recommended that you use either FastCGI or mod_python.
     200
     201
     202Trac also supports [trac:TracOnWindowsIisAjp AJP] which may be your choice if you want to connect to IIS.
     203
     204==== Generating the Trac cgi-bin directory ====
     205
     206In order for Trac to function properly with FastCGI or mod_python, you need to have a trac.cgi file. This is an executable which loads the appropriate Python code. It can be generated using the `deploy` option of [wiki:TracAdmin trac-admin].
     207
     208There is, however, a bit of a chicken-and-egg problem. The [wiki: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:
     209{{{
     210mkdir -p /usr/share/trac/projects/my-project
     211trac-admin /usr/share/trac/projects/my-project initenv
     212trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
     213mv /tmp/deploy/* /usr/share/trac
     214}}}
     215
     216==== Setting up the Plugin Cache ====
     217
     218Some 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.
    194219
    195220== Configuring Authentication ==
     
    213238
    214239----
    215 See also:  TracGuide, TracCgi, TracFastCgi, TracModPython, [wiki:TracModWSGI], TracUpgrade, TracPermissions
    216 
     240See also: [trac:TracInstallPlatforms TracInstallPlatforms], TracGuide, TracCgi, TracFastCgi, TracModPython, [wiki:TracModWSGI], TracUpgrade, TracPermissions