Doing an install on a VPS (or elsewhere), getting funky soul-sucking ruby inline permission messages in your Mongrel logs and feeling extraordinarily frustrated, dumb or both?
Google to the rescue!
This post and this post kept me sane. After installing freeimage and image science, create a .ruby_inline directory inside your tmp directory with the same permissions [...]
If you’re using anything other than fragment caching on pages with forms (and your fragment caching runs after your form blocks), then you’ll likely see Rails freakout on on the 2nd user that submits your cached form. The authenticity_token from the prior user has been cached and Rails is protecting you (I think). So, [...]
If you’re working with a design team that uses the same CSS id and class selector names across multiple CSS files, if you run asset packaging (cache = ‘true’), you’ll bundle all of the CSS files together and your site will probably berserk on you - a fun way to torture your designers who don’t [...]
Enjoy the Holidays with a new 1.9 Dev Release.
Apparently Mongrel and Rails are fairly close to being compatible….
Nice overview here.
Update. PragDave has some rather pragmatic advice for approaching the 1.9 development release. And yes, the last time I looked at my first year college compositions, I noticed more than a few tautologies. [...]
If you’re seeing the message above while working with RSpec and/or Restful Authentication generated code, try commenting out the following line in your Rails environment.rb before running the code generators again:
config.active_record.observers = :user_observer.
You should hopefully see your error message go away. I’m hopeful, at least.
Nice article about Orbitz prototyping and then eventually building its Travel Updater site in Rails. I think it’s almost a perfect story about how Rails can be used in companies with similar projects.
Happened yesterday. Let’s play some Philip Glass Sesame Street music in celebration. List of features here. So, what’s on the roadmap for 3.0?
Nice post here about creating seed data for Rails applications. I used migrations for a while in a previous application and found it to be quite annoying when trying to keep things in synch with numerous migrations over time.
Just briefly following up on my earlier post on efficient Ruby programming by mentioning this good article on Rails performance by Stefan Kaes posted last year on InfoQ.
