[ckan-dev] Packaging theme and model customisations

[James Gardner]

Hi Seb,

On the packaging front we create a new repository called ckanext-XXX on 
bitbucket and use this to create a new package:

paster create -t ckanext ckanext-xxx

Then you would use the extension and plugin APIs to hook your code back 
into main CKAN. See this for the full discussion:

https://bitbucket.org/okfn/ckan/src/5149f503e741/doc/plugins.rst

If you find a case which the existing architecture doesn't cater for, 
we'll need to think of a new way of allowing the code to exist in the 
extension but still be called from CKAN. At the moment there are no ways 
to hook in either middleware or model changes. I've some ideas about how 
both could be done though if needed.

HTH,

James


On 10/02/11 10:39, Seb Bacon wrote:
> Hi,
>
> What's the preferred model for packaging local customisations?  I
> presume plugins should have something to do with it, but the hook
> points or patterns aren't clear to me.  Specifically, I have:
>
> 1) A template override for the homepage, with some custom functionality
> 2) Some local CSS (override layout_base.html?)
> 3) An extension to the package model (two extra fields which aren't
> implemented with PackageExtras
>
> (I realise for (3) PackageExtras would probably be the way to go, but
> for various reasons might not be practical in this case).
>
> Thanks
>
> Seb
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev