Develop Rails 3 applications with your favorites gems without headaches

As today, starting developing a Rails 3 application using the default libraries is very easy, but when we want to use those tools that were great in Rails 2, some problems begin to appear.

These problems aren’t caused in any way due that Rails or the libraries are unstable. What happens is that a lot of plugins and gems had to update their integration with the framework and some chose to create pre-release versions, others to create branches and others just to bump to a new version, which means we have to hunt which version to use and from where in order to get compatible features.

To simplify the work of many people and to encourage the adoption of Rails 3, I decided to create a template that configures the gems I most use in my projects and installs them in the application, along with other tasks that can be easily followed in the script.

If you appreciate this work, please consider to recommend me at Working With Rails.

5 thoughts on “Develop Rails 3 applications with your favorites gems without headaches

  1. I still had problems with the ‘rails3′ branch of factory_girl. Did you get it to work from that branch?

    I had better luck with the 1.2.5 tag (which hasn’t yet been pushed to rubygems), but this worked in my Gemfile:

    gem ‘factory_girl’, :git => ‘git://’, :tag => ‘v1.2.5′

    But even more recently on HEAD they’ve pushed some more changes to make it more Rails3-friendly.

    And as an aside, I didn’t even realize that the templates would still work with Rails3. Good to know!

  2. Hi Bill, the last time I tried the template Factory Girl worked as expected. I will try to create a new RVM gemset and test everything from scratch.

    Thanks for the advice.

    • I am jealous, I am woirkng on my 12” Powerbook, which is a neat machine in many ways, but this term I am woirkng on XML, and some of the XML, and XSL documents can get out of hand. I would imagine that having more real estate would help in many ways.

    • Thank you so much, I was pulling my hair out. For those who are ulfomcortabne mucking around in the registry, I was able to copy the ansicon folder back to the location I had installed it in. cd there from the command line, run : ansicon -u , then cd to the new location and run: ansicon -i . This fixed the problem without me having to directly interface with the registry.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">