http://localhost/ticket/2950 <p> With the latest template, css and js changes in 2.0, there are a number of things that need preparation prior to a production deployment. One of these is: </p> <ul><li>the fanstatic_resources defined in <tt>ckan/lib/fanstatic_resources.py</tt> (bottom of module) should be prepared, and minified. </li></ul><p> This ticket is to: </p> <ul><li>provide a paster command which when run will generate the minified javascript as css files. </li><li>stop the auto-minification of files when CKAN starts up. </li><li>remove reference to the minified files in the <tt>.gitignore</tt> file. </li><li>add instruction to the release process to run this command, and check-in the minified files to the repo. </li></ul><p> ## Background </p> <p> Currently, minification works seamlessly without the need for any preparation when CKAN is started in a development setup. But on a production site, the webserver will (almost certainly) not have write-access to the directories that will contain the minified files. And so the minification will fail, and the site will end up serving the un-minified media, or even *old* minified media. </p> <p> One way around this would be to allow webserver write access to the directory its serving out of. But this is not generally considered good practice. </p> <p> Another method would be to distribute the minified files with CKAN. This ticket describes how to do this without causing a lot of noise in the commit history of the repo. </p> <p> The auto-minifcation occurs when importing <tt>ckan/lib/fanstatic_resources.py</tt>. </p> <p> ## Changing the process slightly </p> <p> The reason for moving away from auto-minifying files at start-up, to minifying files when running a paster command is: </p> <ul><li>we should be distributing the minified files when we make a release (as we do with translation files). This makes it easier to install CKAN from source. </li></ul><ul><li>if we distribute the minified files, then they need to be checked-in to the repo. </li></ul><ul><li>if they are auto-minified, whenever small changes are made, then this will create a lot of noise in the repo. It will be clearer to have the minified-files generated manually as part of the release process. (Or whever we make a deployment internally). </li></ul> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/2950 Trac 0.12.3 icmurray Mon, 01 Oct 2012 19:12:38 GMT http://localhost/ticket/2950#comment:1 http://localhost/ticket/2950#comment:1 <ul> <li><strong>summary</strong> changed from <em>paster commands to prepare codebase for deployment</em> to <em>paster command to minify javascript</em> </li> </ul> Ticket toby Tue, 02 Oct 2012 09:07:18 GMT http://localhost/ticket/2950#comment:2 http://localhost/ticket/2950#comment:2 <p> just a note to say fanstatic will serve minified files if it finds them in production even if they are old so we need to make sure they are up to date. </p> Ticket icmurray Tue, 02 Oct 2012 10:42:44 GMT http://localhost/ticket/2950#comment:3 http://localhost/ticket/2950#comment:3 <ul> <li><strong>description</strong> modified (<a href="/ticket/2950?action=diff&amp;version=3">diff</a>) </li> <li><strong>summary</strong> changed from <em>paster command to minify javascript</em> to <em>paster command to minify javascript and css</em> </li> </ul> Ticket seanh Tue, 02 Oct 2012 14:54:14 GMT http://localhost/ticket/2950#comment:4 http://localhost/ticket/2950#comment:4 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> Ticket