|
| 1 | +ietfdb (6.4.0) ietf; urgency=medium |
| 2 | + |
| 3 | + **Serve static assets via CDN** |
| 4 | + |
| 5 | + This release adds support for serving static files through a CDN, rather |
| 6 | + than having them served by the datatracker webserver. This will both |
| 7 | + offload the datatracker webserver and speed up retrieval of static files. |
| 8 | + |
| 9 | + By default, all external static assets (such as jquery, bootstrap, |
| 10 | + font-awesome, qunit, select2) are served via CDN, while the datatracker's |
| 11 | + own static files are not. It is expected that the more stable datatracker |
| 12 | + static files will be migrated to be served via CDN also, over time. |
| 13 | + |
| 14 | + This release also adds support for easy update of external javascript, font, |
| 15 | + and css libraries by means of a new management command 'bower_install' which |
| 16 | + makes use of the 'bower' package manager. Use of this management command |
| 17 | + requires that bower be installed on the development platform. |
| 18 | + |
| 19 | + When deploying this and following releases, a new action is needed in order |
| 20 | + to make the appropriate static content available for serving via CDN: |
| 21 | + |
| 22 | + After checking out the release and creating the symlink to the new release |
| 23 | + in the datatracker deployment directory, it is now also necessary to create |
| 24 | + a new symlink within a directory which is served through the CDN: |
| 25 | + |
| 26 | + $ ln -s /a/www/ietf-datatracker/$releasenumber/static/lib /www/www6s/lib/dt/$releasenumber |
| 27 | + |
| 28 | + A note about that has been added to the README file in the datatracker |
| 29 | + deployment directory. |
| 30 | + |
| 31 | + -- Henrik Levkowetz <henrik@levkowetz.com> 06 Aug 2015 10:40:46 +0000 |
| 32 | + |
| 33 | + |
1 | 34 | ietfdb (6.3.0) ietf; urgency=medium |
2 | 35 |
|
3 | 36 | **Active area, directorate, team, and area group pages** |
|
0 commit comments