[ckan-dev] Use git submodules to manage recline in CKAN

Thu Apr 12 18:50:36 UTC 2012

Hey,  

we're using them in OpenSpending and they are clearly the right solution in theory. In practice, keeping them in sync, making sure they get deployed when necessary and explaining them to people who just want to play with your codebase has proven a horrible PITA.  

I think we're now moving to a model where the URL of that sub-component is configurable (openspendingjs, as openspending.script_root in the .ini) so people can either check it out into pylons' public/ directory or just set another path (I have apache running locally and share my code root on localhost). The nice side-effect of this is that it forces you to use url builder helpers for assets, so you get asset subdomains, cache-bombing etc. for free.

- Friedrich   

On Thursday, April 12, 2012 at 8:44 PM, Adrià Mercader wrote:

> Hi all,
>  
> I don't have many experience with them, but Rufus mentioned that it
> may be worth using git submodules to manage external repos in CKAN
> source, like recline.
>  
> I had a quick look and they look quite useful, and I think we are
> already using them for some docs theme repo. Has anyone any
> experience, reservations, thoughts about them?
> Will they affect the deployment, packaging process?
>  
> Adrià
>  
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org (mailto:ckan-dev at lists.okfn.org)
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>  
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20120412/314dcfc2/attachment-0001.html>