State Of Flux

I wanted a nice looking 404, 500 and maintenance pages for my Rails app and I couldn’t serve them from Rails.

My requirements were:

• I didn’t want to hand code the pages – I’m using a web framework for a reason!
• I wanted to use the application’s layout
• I needed that pages to be static so I could serve them when the Rails app was either down or when it had ‘issues’

My solution was to:

1. create a controller for the purpose of rendering the static pages
2. tailor your views so you have nice 404, 500 and maintenance pages
3. modify the layout so that signin and register were not longer present
4. create a rake task to render the pages and write them out to a file

Items 1 & 2 are just standard Rails stuff – so go nutz young coders.

Item 3 was pretty straight forward, in the layout I put:

  <% unless controller.controller_name == "errors" %>
     put your sign-in code here
  <% end %>

Item 4 was a bit trickier, but this rake task should get you up and running.

  namespace :generate do
    task :pages => :environment do
      require 'action_controller/integration'
      app = ActionController::Integration::Session.new
      app.host! "stateofflux.com"
      [['/errors/error_404', 'public/40 4.html'],
       ['/errors/error_500', 'public/500.html']].each do |url, file|
        begin
          app.get url
          File.open(file, "w") { |f| f.write app.response.body }
        rescue Exception => e
          puts "Could not write file #{e}"
        end
      end
    end
  end

We run the rake task in the development environment then check it in, but you could run it in production if there was production data that you needed to create the page.

Tags: 404, 500, apache, errorpages, layout, nginx, rails, rake, static

This entry was posted on Monday, July 14th, 2008 at 11:05 am and is filed under Home. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.