On Mon, Mar 15, 2010 at 8:41 AM, Patrick Peak <pea...@gmail.com> wrote: > A. Copy the static files from the gems into the public directory of > the project, which can allow the web server to handle serving them. > (BrowserCMS does this).
I dislike the copying files approach, it seems confusing and error-prone. > B. Have the plugin/gem serve the static assets from the gem through > rails. (There are some plugins that do this whose names I can't > remember). This seems best, especially if this is "below" the rails caching layer, so that they can still be cached on filesystem/memcached/etc and served via webserver, even though they are being 'read' from in-place plugin/gem files via ruby code. > C. Do something fancy with symlinks (if the OS supports them). Sounds like a bad idea too. We should try to be platform-agnostic if at all possible, which it is. -- Chad -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
