search

railsyard / railsyardcms

Railsyard - One Ruby on Rails CMS to rule them all!
www.railsyardcms.org
Other
95 stars 7 forks source link

switching to rails 3.1 because of the asset pipline #4

Closed spieker closed 13 years ago

spieker commented 13 years ago

Hi,

sorry for these many tickets, but I started to create my first design and having a little trouble with placing the assets (images, javascripts and stylesheets). Rails 3.1 has a really great solution for that with the asset pipline. It wouldn't be a big problem doing that, I think, but for me it's a little problem to ensure there are no bugs in the system after updating to rails3.1, because I don't know all features yet.

Would be a really big gain four your system, i think.

Greetings, Paul

spieker commented 13 years ago

http://davidjrice.co.uk/2011/05/25/how-to-upgrade-a-rails-application-to-version-3-1-0.html

spieker commented 13 years ago

sorry, haven't seen, you are using 'themes_for_rails', will try that first ;)

silviorelli commented 13 years ago

Yes I'll surely port Railsyard to Rails 3.1, it shouldn't be very complicated, but I must wait the gems I'm using to become compatible first.

For the assets you can put it in your theme directory and use theme_for_rails helpers like:

current_theme_image_path('logo.png') # => /themes/default/images/logo.png current_theme_stylesheet_path('style') # => /themes/default/stylesheets/logo.css current_theme_javascript_path('app') # => /themes/default/stylesheets/app.js

Btw many many thanks for your commits :D