I like the rake task best. LOL... So I went to implement it and found that there is already a task there. It doesn't have a body because just running rake causes the plugin assets to be copied.
My only question is, how do we now turn off the write without having to change the code? I would like to make that a configuration or something. On Fri, May 8, 2009 at 4:48 PM, Bruno Bornsztein <[email protected]> wrote: > Sure... the template could be modified to run > `EnginesHelper::Assets.propagate`, or rake community_engine:mirror_assets > (copying the CE assets into the apps public directory) and then commit the > files. > > > On Fri, May 8, 2009 at 11:52 AM, Carl Fyffe <[email protected]> wrote: >> >> Does this have to be done at runtime? Or is there a way that it can be >> done before deployment? >> >> On Fri, May 8, 2009 at 7:46 AM, Bruno Bornsztein >> <[email protected]> wrote: >> > Yeah, CE copies everything from public into the plugin assets directory. >> > This applies to other plugins (beside CE) too. For example, the >> > CE_Facebooker plugin relies on this to copy its js and css to the public >> > directory. >> > >> > On Fri, May 8, 2009 at 12:54 AM, Carl Fyffe <[email protected]> >> > wrote: >> >> >> >> Does CE still need to build the plugin_assets directory dynamically? >> >> Are things added to it dynamically? >> >> >> >> If either of the above are yes can you point me to what uses it >> >> besides the stuff that is already there statically? >> >> >> >> Thanks! >> >> >> >> Carl >> >> >> >> >> > >> > >> > > >> > >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/communityengine?hl=en -~----------~----~----~----~------~----~------~--~---
