Changes between Version 4 and Version 5 of TracUpgrade


Ignore:
Timestamp:
Jun 6, 2010 2:50:38 PM (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v4 v5  
    44== Instructions ==
    55
    6 Typically, there are five steps involved in upgrading to a newer version of Trac:
     6Typically, there are seven steps involved in upgrading to a newer version of Trac:
    77
    88=== 1. Update the Trac Code === #UpdatetheTracCode
     
    1313
    1414{{{
    15 # easy_install --upgrade Trac=0.12beta1
     15# easy_install --upgrade Trac==0.12b1
    1616}}}
    1717(once beta1 is released, that is)
     
    6060
    6161{{{
    62 trac-admin /path/to/projenv resync
     62trac-admin /path/to/projenv repository resync '*'
    6363}}}
    6464
    65 === 5. Steps specific to a given Trac version  ===
     65=== 5. Refresh static resources ===
     66
     67If 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{{{
     69trac-admin /path/to/env deploy /deploy/path
     70}}}
     71this will extract static resources and CGI scripts (trac.wsgi, etc) from new Trac version and its plugins into `/deploy/path`.
     72
     73=== 6. Steps specific to a given Trac version  ===
    6674==== Upgrading from Trac 0.11 to Trac 0.12 ====
    6775===== Python 2.3 no longer supported =====
     
    103111If you had the webadmin plugin installed, you can uninstall it as it is part of the Trac code base since 0.11.
    104112
    105 === 6. Restart the Web Server === #RestarttheWebServer
     113=== 7. Restart the Web Server === #RestarttheWebServer
    106114
    107115If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server.