DataMapper and Merb, sharing your errors via the merb display API.
This is a quick little snippet. At Vokle all of our products are built using our core API, which thanks to merb, was a piece of cake. The thing that sucks is sometimes we return objects as JSON via the display API and the "errors" are missing in the event that validation failed. How to fix that?
Throw this somewhere:
1 2 3 4 5 6 7 8 9 10 | module DataMapper module Validate class ValidationErrors def to_json @errors.to_hash.to_json end end end end |
Now in your merb controllers, when you are displaying an object that may have errors:
1 2 3 4 5 6 7 8 | class People < Merb::Controller def create(person) #... *SNIP* ... display @person, nil, {:methods => [:errors]} #... *SNIP* ... end end |
And whatever is getting your data back in XML or JSON (yeah or YAML, right) will get the errors on your object as well. Cool.
Yay, users give you invalid data. Congrats.
MovingParts: Auto versioning your Javascript and CSS
This tutorial has a few moving parts. It could be easily recreated with any stack, but for this post I used Nginx and Merb.
Why?
We like to keep things fast. Two ways we do that is compress the hell out of our js/css and set the cache time on our assets to max. This is cool to do and obvious, the thing that sucks is when its time to roll out new javascript or css making sure the clients get the updates.
What?
For this example I am using merb and merb-assets (w/ my latest merb patch), nginx and ruby-yui.
Step1 - Add version info to assets with merb-assets
In our code base we have a version for our site, set in a variable like WWW_VERSION. Using this variable it is easy (with the newest merb-assets plugin) to modify the path of all of your assets on the fly.
Stick this in your init.rb...
1 2 3 4 5 6 7 8 9 10 11 12 | WWW_VERSION = "0.1.0" # this will make require_js "application" # => /javascripts/application.0.1.0.js # instead of /javascripts/application.js Merb::Plugins.config[:asset_helpers][:js_suffix] = ".#{WWW_VERSION}" Merb::Plugins.config[:asset_helpers][:css_suffix] = ".#{WWW_VERSION}" |
At this point in time merb is going to start outputting modified paths to your assets that contain version numbers. This is cool because now when we modify javascript or css and bump the version number it will cause the clients that have cached the static assets to redownload them since the file path is different. The part that sucks is renaming a bunch of javascript and css files.
Step2 - Lying about file names
Renaming a bunch of files does suck! So don't do it. Instead have that sneaky russian Nginx lie about it for you.
Stick this in you nginx.conf...
1 2 3 4 5 6 7 8 9 10 | location ~ ^/(javascripts|stylesheets) { rewrite ^/(javascripts|stylesheets)\/([^\d]+)(?:\.[0-9]+)*\.(js|css)$ /$1/$2.$3; expires max; break; } |
This rewrite rule will make nginx route any javascript/stylesheet to the original file if it contains a version number. So a request like to '/javascripts/application.0.1.0.js' will be rewritten to '/javascripts/application.js'. Nifty.
Step3 - Compress those assets
You can compress your assets in a number of ways, I'll go with shameless self promotion and recommend RubyYUI. RubyYUI is a ruby wrapper for the Java-based YUI Compressor. It lets you glob paths instead of doing one file at a time and add suffixes to files. All sorts of things.
You can do something like this in a vlad or capistrano task during deployment.
1 2 3 4 5 6 7 8 9 10 | require 'rubygems' require 'ruby-yui' # this will cause the files to be compressed in place Yui.new("./public/javascripts",:stomp => true, :suffix => nil).compress Yui.new("./public/stylesheets",:stomp => true, :suffix => nil, :type=>:css).compress |
Now you have compressed assets in place in your deployed app and nginx will rewrite any versioned paths to your compressed files. Bump your version number and all your clients will start getting the new compressed files. Wee.
