Changes between Version 5 and Version 6 of TracUpgrade


Ignore:
Timestamp:
2010-02-17T07:22:03+01:00 (4 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v5 v6  
    22[[TracGuideToc]] 
    33 
    4 A [TracEnvironment Trac environment] needs to be upgraded before it can be used with Trac 0.11. This document describes the steps necessary to upgrade an environment. 
    5  
    6 Environment upgrades are not necessary for minor version releases unless otherwise noted.  
    7  
    84== Instructions == 
    95 
    10 Typically, there are four steps involved in upgrading to a newer version of Trac: 
     6Typically, there are five steps involved in upgrading to a newer version of Trac: 
    117 
    12 === Update the Trac Code === 
     8=== 1. Update the Trac Code === #UpdatetheTracCode 
    139 
    1410Get the new version as described in TracInstall, or your operating system specific procedure. 
     11 
     12If you installed a recent 0.11 version of Trac via {{{easy_install}}}, it might be the easiest to use it also to upgrade you Trac installation. 
     13 
     14{{{ 
     15# easy_install --upgrade Trac 
     16}}} 
    1517 
    1618If you do a manual (not operating system specific) upgrade, you should also stop any running Trac server before the installation. Doing "hot" upgrades is not advised, especially not on Windows ([trac:ticket:7625 #7265]). 
     
    1820You may also want to remove the pre-existing Trac code by deleting the `trac` directory from the Python `lib/site-packages` directory, or remove Trac .eggs from former versions. 
    1921The location of the site-packages directory depends on the operating system, and the location in which Python was installed. However, the following locations are common: 
    20  * If you’re using Linux: /usr/lib/python2.X/site-packages 
    21  * If you’re using Windows: C:\Python2.X\lib\site-packages 
    22  * If you’re using MacOSX: /Library/Python/2.X/site-packages 
     22 * on Linux: /usr/lib/python2.X/site-packages 
     23 * on Windows: C:\Python2.X\lib\site-packages 
     24 * on MacOSX: /Library/Python/2.X/site-packages 
    2325 
    2426You may also want to remove the Trac `cgi-bin`, `htdocs`, `templates` and `wiki-default` directories that are commonly found in a directory called `share/trac` (the exact location depends on your platform). 
     
    2830If you had the webadmin plugin installed, you can now uninstall it as it is now part of the Trac code base. 
    2931 
    30 === Upgrade the Trac Environment === 
     32=== 2. Upgrade the Trac Environment === #UpgradetheTracEnvironment 
     33 
     34Environment upgrades are not necessary for minor version releases unless otherwise noted.  
    3135 
    3236After restarting, Trac should show the instances which need a manual upgrade via the automated upgrade scripts to ease the pain. These scripts are run via [TracAdmin trac-admin]: 
     
    3741This command will do nothing if the environment is already up-to-date. 
    3842 
    39 Note that if you are using a PostgreSQL database, this command will fail with the message that the environment can only be backed up when you use an SQLite database. This means that you will have to backup the repository and the database manually. Then, to perform the actual upgrade, run: 
     43Note that a backup of your database will be performed automatically prior to the upgrade.  
     44This feature is relatively new for the PostgreSQL or MySQL database backends, so if it fails, you will have to backup the database manually. Then, to perform the actual upgrade, run: 
    4045{{{ 
    4146trac-admin /path/to/projenv upgrade --no-backup 
     
    4449If you are using custom CSS styles or modified templates in the templates directory of the TracEnvironment, you will need to convert them to the Genshi way of doing things. To continue to use your style sheet, follow the instructions at TracInterfaceCustomization#SiteAppearance. 
    4550 
    46 === Update the Trac Documentation === 
     51=== 3. Update the Trac Documentation === #UpdatetheTracDocumentation 
    4752 
    4853Every [TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. As you probably want to keep the included documentation in sync with the installed version of Trac, [TracAdmin trac-admin] provides a command to upgrade the documentation: 
     
    5358Note that this procedure will of course leave your `WikiStart` page intact. 
    5459 
    55 === Site Templates === 
     60=== 4. Resynchronize the Trac Environment Against the Source Code Repository === 
     61 
     62Each [TracEnvironment Trac environment] must be resynchronized against the source code repository in order to avoid errors such as "[http://trac.edgewall.org/ticket/6120 No changeset ??? in the repository]" while browsing the source through the Trac interface: 
     63 
     64{{{ 
     65trac-admin /path/to/projenv resync 
     66}}} 
     67 
     68=== 5. Steps specific to a given Trac version  === 
     69==== Upgrading to Trac 0.11 ==== 
     70===== Site Templates ===== 
    5671The templating engine has changed in 0.11, please look at TracInterfaceCustomization for more information. 
    5772 
    58 === Trac Macros, Plugins === 
     73===== Trac Macros, Plugins ===== 
    5974The Trac macros will need to be adapted, as the old-style wiki-macros are not supported anymore (due to the drop of [trac:ClearSilver ClearSilver] and the HDF); they need to be converted to the new-style macros, see WikiMacros. When they are converted to the new style, they need to be placed into the plugins directory instead and not wiki-macros, which is no longer scanned for macros or plugins. 
    6075 
    61 === For CGI users === 
    62  
    63 For those who run Trac under the CGI environment, run this command in order to obtain the trac.cgi file: 
     76===== For FCGI/WSGI/CGI users ===== 
     77For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file: 
    6478{{{ 
    6579trac-admin /path/to/env deploy /deploy/directory/path 
     
    6882This will create a deploy directory with the following two subdirectories: `cgi-bin` and `htdocs`. Then update your Apache configuration file `httpd.conf` with this new `trac.cgi` location and `htdocs` location. 
    6983 
    70 === Restart the Web Server === 
     84=== 6. Restart the Web Server === #RestarttheWebServer 
     85 
    7186If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server. 
    7287 
    7388== Known Issues == 
     89 
    7490=== parent dir === 
    7591If you use a trac parent env configuration and one of the plugins in one child does not work, none of the children work. 
     92 
    7693=== some core modules won't load ===  
    7794This can happen in particular with Python 2.3 on Windows when upgrading without uninstalling first. 
     
    8198}}} 
    8299Remove the `Lib/site-packages/trac` folder and reinstall. 
     100 
    83101=== Wiki Upgrade === 
    84 `trac-admin` will not delete or remove pages that were in version 0.10 but now are not in version 0.11, such as WikiMacros. 
     102`trac-admin` will not delete or remove default wiki pages that were present in a previous version but are no longer in the new version. 
     103 
    85104 
    86105== Changing Database Backend == 
    87 == SQLite to PostgreSQL == 
     106=== SQLite to PostgreSQL === 
    88107 
    89108The [http://trac-hacks.org/wiki/SqliteToPgScript sqlite2pg] script on [http://trac-hacks.org trac-hacks.org] has been written to assist in migrating a SQLite database to a PostgreSQL database