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

[David Raznick]

Hello

Have anyone tried fanstatic?  http://www.fanstatic.org/en/0.11.2/index.html

It essentially lets you put your js/css dependencies in a python package
and it will inject it into your html for you and serve them. It already has
packages on pypi for things like backbone and bootstrap.  Adding a recline
package on pypi would seem to make sense and would be generally good to do
anyway.

It may be a heavyweight solution but I think it would also work much better
for the current way we do our dependencies and debian packaging. It also
will do our minifying, cache invalidation for us and easy config to switch
them off for development.  I am not sure how will in works for subdomains
and not root script paths though.

I have not used it and am slightly wary of another dependency but it seems
like exactly what is needed.

David


On Thu, Apr 12, 2012 at 7:50 PM, Friedrich Lindenberg <
friedrich.lindenberg at okfn.org> wrote:

> 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
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
>
>
> _______________________________________________
> ckan-dev mailing list
> 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/20120413/40afac12/attachment-0001.html>