Here are a couple of issues I faced when installing:

• Rails 2.3.2 is just released. So, I wanted to use latest and greatest codebase for my solution. However, it seems that latest Spree (version 0.7.0) requires rails version 2.2.2. I found the line that checks for this and tried to change it to 2.3.2 but it failed at runtime. Fair enough, spree 0.7.0 isn’t tested with 2.3.2 yet. I switched back to 2.2.2. And I had to install rails 2.2.2 (in addition to rails 2.3.2 that I have already upgraded to.
• Once I installed rails 2.2.2, I was able to generate a base project using “spree <project name>”. command. I was able to perform “rake db:boostrap” to fill fake data. And then, “script/server” to see that everything is fine. All is great so far. Now, as any serious project, I wanted to freeze rails, all gems used including spree itself. I tried “rake rails:freeze:edge RELEASE=2.2.2″ which installed rails 2.2.2 in my vendor/rails directory. However, it replaced my config/boot.rb with that a rails 2.2.2 app should have. This broke Spree since Spree modifies this file extensively. I had to regenerate a separate spree project to get a valid boot.rb.  I can only hope that frozen rails 2.2.2 and the boot.rb are compatible now. I can still launch my spree app fine.

Next, I will looking at freezing all gems used. And, then it will be time to hit the googlegroups for how to use/customize spree codebase.

Anybody has any more experience with this?

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.