I checked up on ActiveRecord::Tableless and saw a fork that had some promising changes in, so I set out to pull those changes back to my repo. Seemed simple enough, I followed Steven Bristol’s steps and it worked.
The changes made by Peter Wagenet were simple and very useful, thanks Pete!
I’ll start working on specs for the project closer to the end of the week, for now my focus is on getting BIND DLZ on Rails ready for its first public appearance.
Just picked up this detailed post for using git on Windows, thought I’d share it here too. And just in time as well, I’ve spent a lot of time the last couple of days reading up on Adobe Air and making notes of possible applications I can play with in the coming months. Especially using Air on Linux.
Now the thought of pushing some Air apps to github just became a reality, might help with the cross-pollination of git and air inside different communities…
Watch this space for some future Air apps sitting on a RESTful Ruby backend.
Surely your Rails app flies, no request takes longer than 60 seconds to complete, ever. You’ve proven that Rails can scale and all that jazz. Surely you’ve really spent the time to read the nginx wiki and customize Ezra’s nginx.conf to such a degree that you can handle thousands of concurrent requests at any given time. You know, Rails scales…
Now some of us develop fairly intricate systems using Rails. Systems that have long running reports, or systems that connect to other systems to execute commands, or obtain information. Whatever the reason, somethings just can’t complete within 60 seconds, and if your users understands the complexity of the background tasks they’ll quite happily press a button and go make coffee while the server crunches away at the reports.
I head one such project, and had the most interesting issue I just solved. And it involved reading a lot on nginx’s fine print…
Keeping with the exodus from SVN/Mercurial to git, here is a super quick guide for converting a Mercurial repo to git.
1. Get the fast-export script via git
git clone git://repo.or.cz/fast-export.git
2. Make a new (empty) git repo for the project that is currently in Mercurial
git init projectname.git
3. Use fast-export to do the convertion
cd projectname.git /path/to/fast-export.git/hg-fast-export.sh -r /path/to/project.hg git checkout master
4. (Optionally) use rsync to bring over uncommitted changes
rsync -av --delete-after --exclude=.git --exclude=.hg /path/to/project.hg /path/to/project.git
5. Enjoy your new git repo 
I’ve only followed these steps on projects that are in their infancy, and were used as Mercurial experiments. I’m not sure how well branches and tags will be handled by the script. Any feedback would be welcome.
