| 4 | | Trac environments sometimes need to be upgraded before they can be used |
| 5 | | in a new version of Trac. This document describes the steps necessary |
| 6 | | to upgrade an environment. |
| | 4 | A Trac environment sometimes needs to be upgraded before it can be used with a new version of Trac. This document describes the steps necessary to upgrade an environment. |
| | 5 | |
| | 6 | '''Note''': ''Environment upgrades are not necessary for minor version releases unless otherwise noted. For example, there's no need to upgrade a Trac environment created with (or upgraded) 0.8.0 when installing 0.8.4 (or any other 0.8.x release).'' |
| | 7 | |
| | 8 | == Upgrade Synopsis == |
| | 9 | |
| | 10 | A typical upgrade looks like the following: |
| | 11 | |
| | 12 | 1. You upgrade the Trac source code - from an offical release or from a source checkout. |
| | 13 | 2. You run the `trac-admin upgrade` command to bring the database up-to-date with the new Trac code. The table structure changes over time, but it is versioned. The upgrade command find the current version of the DB and the version required by the code, and performs an upgrade if required. |
| | 14 | 3. Optionally, you can run the `wiki upgrade` command to bring the default Wiki pages up-to-date. Your `WikiStart` page will be left intact, of course. |
| | 15 | |
| | 16 | == From 0.8.x to 0.9 == |
| | 17 | |
| | 18 | The database schema was changed between 0.8.x and 0.9. Existing environments must be upgraded before they can be used with Trac 0.9. |
| | 19 | |
| | 20 | The following command will automatically perform the upgrade: |
| | 21 | {{{ |
| | 22 | $ trac-admin /path/to/projectenv upgrade |
| | 23 | }}} |
| | 24 | |
| | 25 | Trac environments are created with a default set of wiki pages. It's recommended to update these pages on existing environments whenever Trac is upgraded to get up-to-date documentation and additional functionality. The following command will perform the update: |
| | 26 | {{{ |
| | 27 | $ trac-admin /path/to/projectenv wiki upgrade |
| | 28 | }}} |
| | 29 | |
| | 30 | If you're using [wiki:TracModPython mod_python], you will need to change the name of the mod_python handler in the Apache HTTPD configuration: |
| | 31 | {{{ |
| | 32 | from: PythonHandler trac.ModPythonHandler |
| | 33 | to: PythonHandler trac.web.modpython_frontend |
| | 34 | }}} |
| | 63 | == Upgrading SQLite from 2.x to 3.x == |
| | 64 | |
| | 65 | The database formats used by SQLite 2.x and sqlite 3.x are incompatible. If you upgrade your SQLite version (this can also happen implicitly if you upgrade from PySQLite 1.0.x to 1.1.x or 2.x), then you must convert your database. |
| | 66 | |
| | 67 | To do this, install both SQLite 2.8 and SQLite 3.x (they have different filenames so can coexist in the same directory). Then use the following commands (Windows): |
| | 68 | {{{ |
| | 69 | $ mv trac.db trac2.db |
| | 70 | $ sqlite trac2.db .dump | sqlite3 trac.db |
| | 71 | }}} |
| | 72 | |
| | 73 | Then when you're happy with the conversion and tested everything you can delete the trac2.db file. |
| | 74 | |
| | 75 | For more information see http://www.sqlite.org/version3.html |
| | 76 | |
