Changes between Version 2 and Version 3 of TracUpgrade
- Timestamp:
- 08/22/11 13:23:41 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracUpgrade
v2 v3 4 4 == Instructions == 5 5 6 Typically, there are fivesteps involved in upgrading to a newer version of Trac:6 Typically, there are seven steps involved in upgrading to a newer version of Trac: 7 7 8 8 === 1. Update the Trac Code === #UpdatetheTracCode … … 13 13 14 14 {{{ 15 # easy_install --upgrade Trac= 0.12beta115 # easy_install --upgrade Trac==0.12b1 16 16 }}} 17 17 (once beta1 is released, that is) … … 60 60 61 61 {{{ 62 trac-admin /path/to/projenv re sync62 trac-admin /path/to/projenv repository resync '*' 63 63 }}} 64 64 65 === 5. Steps specific to a given Trac version === 65 === 5. Refresh static resources === 66 67 If you've setup web server to give out static resources directly (accessed using /chrome/ URL) then you need to refresh them using the same command: 68 {{{ 69 trac-admin /path/to/env deploy /deploy/path 70 }}} 71 this will extract static resources and CGI scripts (trac.wsgi, etc) from new Trac version and its plugins into `/deploy/path`. 72 73 Some web browsers cache the CSS and Javascript file in a strong way, so you'll perhaps need to refresh the cache of the browsers by a force reload (and tell your users to do so!). 74 75 === 6. Steps specific to a given Trac version === 66 76 ==== Upgrading from Trac 0.11 to Trac 0.12 ==== 67 77 ===== Python 2.3 no longer supported ===== … … 103 113 If you had the webadmin plugin installed, you can uninstall it as it is part of the Trac code base since 0.11. 104 114 105 === 6. Restart the Web Server === #RestarttheWebServer115 === 7. Restart the Web Server === #RestarttheWebServer 106 116 107 117 If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server.