Ruby

Rack is the HTTP interface for Ruby. Rack defines a standard interface for interacting with HTTP and connecting web servers. Rack makes it easy to write HTTP facing applications in Ruby. Rack applications are shockingly simple.

The answer is simple: stop using rake. Odds are you're using rake as a way to run ruby code. Instead create a CLI to do the the thing. This should make you consider how to design, thus how to test it, and thusly create better software. You'll thank me in time.

Ruby has a logging built in. Simply require logger and you're off to the races. Don't waste your time with log4r or anything else. The standard logger is good enough for almost every use case I've heard of. Less dependencies are always important. Use the standard library when you can.

Pages are composed of different components. Each component has their own presenter. A page presenter will provide an interface for getting a presenter for each component. That presenter is passed into the partial as a local variable. It works out pretty well.