Updated for Caterpillar v2. Need to think about how setLogger should work, or if it should still be here.
Removed setLogger. Renamed last logger to console logger. Added docpad-debug.log output if we are running in debug log level.
merged
Got caterpillar v2 working

- Remove the debug log file on startup
- Turn off colors for the debug stream
- Only re-add the console to stdout pipe if we removed it
- Added debugLogPath property to docpad instance
v6.32.0. Bugfix. Improvement.

- v6.32.0 May 2, 2013
	- Now uses [Caterpillar](https://github.com/bevry/caterpillar) v2
	- We now write a `docpad-debug.log` file when running with the `-d`
flag, submit this when you file a bug report :)
	- Fixed colors not showing on custom Terminal color schemes
	- Fixed a double progress bar issue when a log message occurs when the
progress bar is being written
	- Removed `setLogger()` instead you should do `getLogger()` and pipe
the results to where you need
	- Added `getLoggers()` to fetch all the different logger streams we
are using, generally there are:
		- `logger` the stream we write log messages to
		- `console` the stream that is outputted to stdout
		- `debug` the stream that is outputted to the debug log file