hi, just wanted to mention my two cents :)
we use fanstatic and less in our pyramid application. both things are great (though i don't know about webassets yet). first we had the ``lessc`` in pyramid as explained here: http://www.gawel.org/weblog/en/2011/12/Using_lesscss_with_pyramid_and_fanstatic this has several disadvantages: - compilation of a ``less`` file to ``css`` causes the app to restart, as lessc is run on start (too slow) - lessc must be in the path when starting the app; useless restriction on a production machine and a little hazzle in a buildout environment with self-built nodejs - no option to add another build-step like compressing the ``css`` files we dropped the solution above and i just built a simple nodejs script that watches our files and compiles on demand (really short latency, no app restart). this watcher is automatically started in the local ``supervisord``, which is configured by buildout. on production there is no lessc or anything nodejs-related. fanstatic itself - just to mention that - is great for us because of the excellent resource handling and the ability to package and version static files on production. hope this helps, andi On 05.11.2012, at 20:08, Petr Blahos wrote: > > You could have a look at miracle2k/webassets or tav/assetgen. > Both have pyramid integration projects and both handle content-hash-based > automatic recompilation. > > webassets look good. Somehow it feels better than fanstatic. Now I am > starting to > thing in a different direction, which is: If I am in a debug mode, I will > start a thread > directly in my pyramid app (probably in a modified pyramid_webassets), which > will > take care of the periodic compilation of the resources. Meaning, not when > they are > required, but when sources change (based on a set of bundles defined in > webassets). > > Thanks for your pointers. > -- > Petr > > > > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to pylons-discuss@googlegroups.com. > To unsubscribe from this group, send email to > pylons-discuss+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
