casperfabricius.com

7 Responses to “Hosting a Spree webshop on Heroku”

1. uberVU - social comments
   October 18th, 2009 at 4:27 pm

   

   Social comments and analytics for this post…

   This post was mentioned on Twitter by fabricius: Hosting a Spree webshop on Heroku http://ff.im/-a3yTQ...

2. Magne K. Davidsen
   November 5th, 2009 at 12:40 am

   

   Hey Casper!

   Thanks for a great blog post. I followed the steps in the instructions, and it works perfectly.

   However, I would like to clone the spree source code, install the heroku extension, and deploy to Heroku.

   When I try this, I get an error saying

   “/usr/local/lib/ruby/1.8/fileutils.rb:1262:in `initialize’: Read-only file system”

   I followed the exact same steps as for the spree gem. Do you have any ideas why this does not work?

   Thanks a lot!

3. Casper Fabricius
   November 5th, 2009 at 10:10 am

   

   Hi Magne,

   Glad you could use it. As for the error you get when cloning the Spree master repository, it could be for a number of reasons. Obviously the error is related to some code trying to write to disk, but as you haven’t included the stacktrace, I can’t see where it happens. Most likely it is Rails trying to cache some stylesheets or javascripts.

   I have patched one specific error related to that I got with the 0.9.1 gem, but this can easily have changed in the “edge” version of Spree you get by cloning the repository. I will upgrade my extension to work with 0.9.2 when I have the time (perhaps it already does, you tell me?), but I can’t really play catch up with the edge version of Spree ;)

   Cheers,
   Casper

4. Magne K. Davidsen
   November 5th, 2009 at 11:47 am

   

   First of all, thanks for the quick answer!

   Your extension already works with 0.9.2, so that is not the problem. I just changed the dependency :)

   The stack trace can be seen here (at least for the time being):
   http://spree-heroku-troublesome.heroku.com/

   I must admit I don’t have to much experience with RoR, but I can’t really understand from this trace what part of the app that tries to do filewriting. The blank_iframe.html doesn’t really do anything.

   Of course, it may be the caching of stylesheets you’re mentioning… Is there anyway to disable all caching in Rails?

   Thanks again!

5. Casper Fabricius
   November 9th, 2009 at 8:14 pm

   

   Hi Magne,

   Sorry to keep you waiting a bit longer this time. Nothing is clear from the stacktrace, since for the interesting part is just says ” … 34 levels…” ;)

   However, I’d guess that it is trying the write the blank_iframe.html file – or perhaps delete it? Do you have some sort of extension that tries to generate this file perhaps?

   /Casper

6. Nalin
   February 16th, 2010 at 12:59 am

   

   Hi Casper, great extension. Was wondering what’s the best way to turn off the extension in dev mode?

   Thanks for your help!

7. Casper Fabricius
   February 16th, 2010 at 10:18 am

   

   Well, I’m pretty sure it works just like plugins: By default, all extensions are loaded alphabetically, and if you want it any other way you must specify the extensions you want to load in the config.

   So, and I have not tested this, you could probably put something like this in your config/development.rb:

   config.extensions = [:site, ... (other extensions, but not :heroku)]
   

   Hope this helps :)