Changes between Version 122 and Version 123 of TracUpgrade
- Timestamp:
- Nov 28, 2016, 10:33:46 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracUpgrade
v122 v123 60 60 === 5. Refresh static resources 61 61 62 If you have set up a web server to give out static resources directly (accessed using the `/chrome/` URL) then you will need to refresh them using the same command:62 If you have configured your web server to serve static resources directly (accessed using the `/chrome/` URL) then you will need to refresh them using the [TracInstall#MappingStaticResources same command]: 63 63 {{{#!sh 64 64 trac-admin /path/to/env deploy /deploy/path 65 65 }}} 66 66 67 This will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`. 68 69 Some web browsers (IE, Opera) cache CSS and Javascript files aggressively, so you may need to instruct your users to manually erase the contents of their browser's cache, a forced refreshed (`<F5>`) should be enough. 67 This will extract static resources and CGI scripts (`trac.wsgi`, etc) from the new Trac version and plugins into `/deploy/path`. 68 69 {{{#!div style="border: 1pt dotted; margin: 1em" 70 **Note:** Some web browsers (IE, Opera) cache CSS and Javascript files, so you should instruct your users to manually erase the contents of their browser's cache. A forced refreshed (SHIFT + <F5>) should be enough. 70 71 {{{#!comment 71 72 Remove above note once #9936 is fixed. 73 }}} 72 74 }}} 73 75