Migrated mzk.me to Doozer

I spent all of 20 minutes today migrating mzk.me over to Doozer 0.1.4.

In the process, I realized that there is no way to specify a Doozer version dependency from within a project.

Right now, this isn't a huge deal since I'm only running Doozer on two apps. But it could quickly get out of hand if I start adding new features.

This seems like it should be pretty trivial. I'll work on it as time permits.

Introducing: Doozer MVC Rack Middleware

I just posted a version patch for the Doozer project I released earlier this week.

Doozer is a lightweight, Rack compatible, MVC framework built with Ruby I've been working on here and there since December 2008.

It borrows a few rails conventions. It comes with a project and file generator to get busy with. It currently features initialization support for ActiveRecord, DataMapper, or Sequel. It also features support for clustering out of the box.

So far, it's turning out to be pretty handy. But before that, how about some background info?

Nice Rack!

Rack is a simple Ruby middleware framework inspired by WSGI. It allows you to define applications, chain them together, and then map them to request paths. It also features adapters for many http servers (mongrel, thin, webrick, etc.).

Doozer is a piece of Rack middleware which globs onto root requests. However, it also allows you to override this behavior if you want to map a specific path outside of Doozer. In addition, you can also define routes and have them processed by Doozer or have them handed off to a sub-application within the Doozer middleware.

Test Coverage

I finally added the foundation for testing the Doozer gem. I would say the test coverage is only 5% as of now. So, I have some more tests to write.

Git Cheat Sheet

I came across this ultra dope git cheat sheet. It's missing a cheat for deleting files.

Never fear.

All you need to do is delete the file and on the next bulk commit it's automatically removed.

Or, you can run 'git rm filename'.

Reboot, Reload, Retool

I scrubbed the old Typo blog and decided to roll my own. This should hopefully give me the old kick in the arse to actually write about all the code related nuggets I find on a daily basis.

We'll see how it goes.