As with most web projects, there's always some little new glitch that pops up. We've been building and massaging our own analytics back end for Riding Resource for some time now, and the change of year from 2009 to 2010 brought some new quirks that had to be dealt with.
While ...
So Riding Resource was developed in Ruby on Rails, as many of you may know. At some point this year I made the switch from using a local Subversion source control system to using git with Github, which has been pretty good. The one pain I was having, ...
Ruby on Rails is pretty neat stuff. Whenever I try to find out how to do something, it seems that I'm not the first to look. And, fortunately, many have usually solved that problem before. One thing that bugged me with Riding Resource was error pages. Sure, Rails allows you ...
We wanted to be able to get some analytics for the various facilities on RidingResource, and that required some thinking. While Google Analytics is certainly great, and we use it heavily, there are some things that it can't capture that are valuable data to both us and our customers.
Since RidingResource ...
One of the things that we decided would be a good idea for RidingResource was to let users of the site contact the various facilities that we have listed. We also wanted to make sure those facilities knew we helped facilitate that contact by injecting some extra information into the ...
I know there are quite a few tutorials and links out there on building an API for your Ruby on Rails application, but I figured that I would document a little bit about how it was done for Riding Resource, but at a high level. A partner had requested access ...
As many of you may already know, Riding Resource has been up and running since January 1st, and we're chugging right along. One thing we realized we wanted was to have people be able to send us their contact information to sign up for a mailing list.
Because we haven't implemented ...
So, for one reason or another, I am using the built-in db store for sessions on the RidingResource site. I was about to embark on a path to utilizing sessions to help maintain the search selections across the site, and I noticed that the sessions database was full of... junk.
Rails ...
The other day I wrote about needing to blank default values when text input fields gain focus in a form. I had found a jQuery-based script that seemed to do the trick... or so I thought.
When RidingResource went beta, I was tailing the RoR logs and noticed that "ZIP" was ...
So while this might seem intuitive, I found it a little tricky. Preliminary Google searching didn't reveal anything inherently obvious. However, robbrit on Freenode was able to lend me a hand and I got it figured out.
As you might expect, restful_authentication's before_filter, :login_required, will direct you to the sessions controller ...
