Deploying a Rails 3.1 app in production

https://moocode.com/posts/1-deploying-a-rails-3-1-application-to-production

by vijaydev • 15 years ago

46 13 15 years ago

firemanx• 15 years ago

I found this really helpful. I'm a little surprised at the inconsistency of the asset pipeline deployment though. I guess we're all supposed to use erb templates if we intend to use it and include images in our stylesheets?

It strikes me as really strange that they would allow certain functionality which you would get used to in development (images in stylesheets that are automatically matched to assets), then have that completely break when you precompile for production.

jarin3• 15 years ago

I couldn't post this in the Facebook comments on the post, but you can fix the Rake 0.9.0 error by putting the following right before load_tasks in your Rakefile:

    module ::MyAppName
      class Application
        include Rake::DSL
      end
    end

    module ::RakeFileUtils
      extend Rake::FileUtilsExt
    end

There's a fix on the way, too.

Also, I believe if you're using SASS/SCSS you can interpolate the asset like so, without having to use erb:

    background: #00ff00 url(#{asset_path 'rails.png'}) no-repeat fixed center;

moomerman3• 15 years ago

Thanks for the info, I'll update the post shortly. Out of interest, what was wrong with the FB comments? I only started using it yesterday because disqus doesn't have a HTTPS option (that I could find anyway).

jarin3• 15 years ago

Oh, it seems to trip out on double colons. If I wasn't being lazy I would have just posted a gist.

rabbitonrails2• 15 years ago

Thanks for the sass inline tip..dont know why i didnt think of that

moomerman3• 15 years ago

I just tried the SCSS trick but the generated CSS was:

    background: lime url(asset_path "rails.png") no-repeat fixed center;

jarin3• 15 years ago

Ah, yeah I forgot, that syntax is used for SassScript. I guess erb is the way to go then.

rabbitonrails2• 15 years ago

also -- the DSL trick doesnt seem to work on heroku (?)..ive had to force 0.8.7 there

getsat• 15 years ago

Half my rake tasks in production will NOT work with this hack in place. I amended my similar comment.[1]

Rake 0.9.0 is extremely broken. I recommend reverting to 0.8.7.

[1] http://news.ycombinator.com/item?id=2572790

bguthrie• 15 years ago

Correct me if I'm wrong, but can't you avoid compiling in production if you package everything as part of your CI build? Rather than deploy off of a git clone, you compile at the end of CI, vendorize your gems, generate a tarball, and push that up.

This minimizes production dependencies (including the need to compile gems live) as long as your CI environment sufficiently resembles prod.

moomerman3• 15 years ago

That could be one solution, however there are some problems that spring to mind like deploying to different architectures (common if you're using EC2) - I guess this fits your point about your CI env resembling prod.

asolove• 15 years ago

It would be fantastic if someone would release a capistrano/rails plugin that lets you specify when to build the assets and where to send them, for those of us who have static assets on different servers from production Rails apps.

smiler• 15 years ago

Why can't someone = you?

Deploying a Rails 3.1 app in production

Related Stories