tracupgrade
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | tracupgrade [2015/06/09 15:23] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Upgrade Instructions ====== | ||
+ | [[: | ||
+ | |||
+ | 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. | ||
+ | |||
+ | | ||
+ | |||
+ | ===== General Instructions ===== | ||
+ | |||
+ | Typically, there are four steps involved in upgrading to a newer version of Trac: | ||
+ | |||
+ | ==== Update the Trac Code ==== | ||
+ | |||
+ | Get the new version of Trac, either by downloading an offical release package or by checking it out from the [[http:// | ||
+ | |||
+ | If you're doing a major version upgrade (such as from 0.8 to 0.9), it is //highly// recommended that you first remove the existing Trac code. To do this, you need to delete the `trac` directory from the Python `lib/ | ||
+ | |||
+ | If you have a source distribution, | ||
+ | < | ||
+ | python setup.py install | ||
+ | </ | ||
+ | |||
+ | |||
+ | to install the new version. If you've downloaded the Windows installer, you execute it, and so on. | ||
+ | |||
+ | ==== Upgrade the Trac Environment ==== | ||
+ | |||
+ | Unless noted otherwise, upgrading between major versions (such as 0.8 and 0.9) involves changes to the database schema, and possibly the layout of the [[: | ||
+ | < | ||
+ | trac-admin / | ||
+ | </ | ||
+ | |||
+ | |||
+ | This command will do nothing if the environment is already up-to-date. | ||
+ | |||
+ | 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: | ||
+ | < | ||
+ | trac-admin / | ||
+ | </ | ||
+ | |||
+ | |||
+ | ==== Update the Trac Documentation ==== | ||
+ | |||
+ | Every [[: | ||
+ | < | ||
+ | trac-admin / | ||
+ | </ | ||
+ | |||
+ | |||
+ | Note that this procedure will of course leave your `WikiStart` page intact. | ||
+ | |||
+ | ==== Restart the Web Server ==== | ||
+ | |||
+ | In order to reload the new Trac code you will need to restart your web server (note this is not necessary for [[: | ||
+ | |||
+ | ===== Specific Versions ===== | ||
+ | |||
+ | The following sections discuss any extra actions that may need to be taken to upgrade to specific versions of Trac. | ||
+ | |||
+ | ===== From 0.9.x to 0.10.x ===== | ||
+ | |||
+ | Due to some changes in the Wiki syntax, you may notice that certain parts of your pages no longer work as expected: | ||
+ | * Previously, links to images would result in that image being embedded into the page. Since 0.10, links to images remain plain links. If you want to embed an image in the page, use the `[[: | ||
+ | * You can no longer use `%20` in wiki links to encode spaces. Instead, you should quote the name containing spaces (for example, use `wiki:" | ||
+ | |||
+ | Several enhancements have been made to the version control subsystem, in particular for the support of scoped repositories has been improved. | ||
+ | It is recommended that you perform a [[: | ||
+ | |||
+ | Also note that the argument list of the [[: | ||
+ | < | ||
+ | | ||
+ | </ | ||
+ | |||
+ | The new usage is: | ||
+ | < | ||
+ | | ||
+ | </ | ||
+ | |||
+ | If you're using any scripts that automate the creation of Trac environments, | ||
+ | |||
+ | ===== From 0.9.3 to 0.9.4 ===== | ||
+ | |||
+ | There is a bug in Pysqlite 1.x that causes reports using the " | ||
+ | |||
+ | ===== From 0.9.x to 0.9.3 or later ===== | ||
+ | |||
+ | If you are using plugins you might need to upgrade them. See http:// | ||
+ | |||
+ | ===== From 0.9-beta to 0.9 ===== | ||
+ | |||
+ | If inclusion of the static resources (style sheets, javascript, images) is not working, check the value of the `htdocs_location` in trac.ini. For [[: | ||
+ | |||
+ | If you've been using plugins with a beta release of Trac 0.9, or have disabled some of the built-in components, you might have to update the rules for disabling/ | ||
+ | |||
+ | If you want to enable the display of all ticket changes in the timeline (the “Ticket Details” option), you now have to explicitly enable that in [[: | ||
+ | |||
+ | < | ||
+ | [[: | ||
+ | ticket_show_details = true | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== From 0.8.x to 0.9 ===== | ||
+ | |||
+ | [[: | ||
+ | < | ||
+ | from: PythonHandler trac.ModPythonHandler | ||
+ | | ||
+ | </ | ||
+ | |||
+ | |||
+ | If you have [[http:// | ||
+ | |||
+ | To do this, you need to have both SQLite 2.8.x and SQLite 3.x installed (they have different filenames so can coexist on the same system). Then use the following commands: | ||
+ | < | ||
+ | $ mv trac.db trac2.db | ||
+ | $ sqlite trac2.db .dump | sqlite3 trac.db | ||
+ | </ | ||
+ | |||
+ | |||
+ | To update multiple database files at once on linux you may use the following command (replace /// | ||
+ | < | ||
+ | $ find /var/trac/ -iname " | ||
+ | </ | ||
+ | |||
+ | |||
+ | Remember the give the webserver write permission to trac.db. | ||
+ | |||
+ | After testing that the conversion was successful, the `trac2.db` file can be deleted. For more information on the SQLite upgrade see http:// | ||
+ | |||
+ | ===== From 0.7.x to 0.8 ===== | ||
+ | |||
+ | 0.8 adds a new roadmap feature which requires additional permissions. While a | ||
+ | fresh installation will by default grant ROADMAP_VIEW and MILESTONE_VIEW | ||
+ | permissions to anonymous, these permissions have to be granted manually when | ||
+ | upgrading: | ||
+ | < | ||
+ | $ trac-admin / | ||
+ | $ trac-admin / | ||
+ | </ | ||
+ | |||
+ | |||
+ | ----- | ||
+ | See also: TracGuide, TracInstall | ||
tracupgrade.txt · Last modified: 2015/06/09 15:23 by 127.0.0.1