Thanks for the helpful input guys! I may end up just using a generator to move a dir to Rails public. That would work, I just prefer the idea of the Gem encapsulating everything so that when a user updates the Gem they will have all the new assets without having to run an "update" task or generator.
Elliott G On Sep 15, 8:00 pm, Marnen Laibow-Koser <li...@ruby-forum.com> wrote: > Elliott Golden wrote: > > I am working on a Rails CMS gem. I want the Gem to have its own Public > > dir (like Rails) to hold css/js/images etc... I have been trying a lot > > of different pathing options from my Gem-centric views, but no matter > > what I try I can't target any of the files. > > > Any thoughts on how to set this up? > > ln -s mygem/public RAILS_ROOT/public/mygem > > I'm not convinced that this is a great idea. > > > > > Thanks, Elliott G > > Best, > -- > Marnen Laibow-Koserhttp://www.marnen.org > mar...@marnen.org > > Sent from my iPhone > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
