Changes between Version 2 and Version 3 of TracUpgrade

Timestamp:

08/22/11 13:23:41 (13 years ago)

Author:

trac

Comment:

--

TracUpgrade

@@ -4 +4 @@
 == Instructions ==
 
-Typically, there are five steps involved in upgrading to a newer version of Trac:
+Typically, there are seven steps involved in upgrading to a newer version of Trac:
 
 === 1. Update the Trac Code === #UpdatetheTracCode
@@ -13 +13 @@
 
 {{{
-# easy_install --upgrade Trac=0.12beta1
+# easy_install --upgrade Trac==0.12b1
 }}}
 (once beta1 is released, that is)
@@ -60 +60 @@
 
 {{{
-trac-admin /path/to/projenv resync
+trac-admin /path/to/projenv repository resync '*'
 }}}
 
-=== 5. Steps specific to a given Trac version  ===
+=== 5. Refresh static resources ===
+
+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:
+{{{
+trac-admin /path/to/env deploy /deploy/path
+}}}
+this will extract static resources and CGI scripts (trac.wsgi, etc) from new Trac version and its plugins into `/deploy/path`.
+
+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!).
+
+=== 6. Steps specific to a given Trac version  ===
 ==== Upgrading from Trac 0.11 to Trac 0.12 ====
 ===== 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.
 
-=== 6. Restart the Web Server === #RestarttheWebServer
+=== 7. Restart the Web Server === #RestarttheWebServer
 
 If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server.