[ckan-dev] Making sure a CKAN 2.0 instance has up to date CSS

[John Martin]

Hullo,

I just wanted to clear up a couple of points that haven't been that clear because of a lack of documentation.

If you are deploying a CKAN instance from a work in progress branch (e.g. the current `release-v2.0` branch) you need to make sure that you run a `paster front-end-build`. This will ensure that the instance has got the most up to date front end dependancies from CKAN core.

Also, from now on whenever a pull request touches anything that can make it into `main.css` the reviewer/merger must make sure they run `./bin/less --production` after they merge the pull request into master and commit any changes that `./bin/less --production` provides. This will mean that when people install from source they get the most up to date CSS.

Bit of context: We don't run `paster front-end-build` on master as it creates unnecessary noise in the repo. The release manager will only run and merge it as we're getting a release branch ready for live. So if you are running from a official release branch you won't have to worry about these issues.

Fore more info docs on ./bin/less is at http://docs.ckan.org/en/latest/frontend-development.html

Cheers,
John Martin
Front End Developer, CKAN

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130327/4ef10580/attachment.html>