properly eggify the watchdog
install watchdog via playbook
create the watchdog configuration file from ploy.conf
don't put config into etc

watchdog is a much simple installation and doesn't require any sub directories
typo
don't honor robots.txt

we are testing our own instance, so there shouldn't be an enthical issue here :)
drive-by fix: update to newer version of ploy
also configure the app for the watchdog
update readme
use the same key for the testing secret everywhere
properly force installation of newer egg

this is only relevant during development though, when newer versions still come with the same version identifier
make history file location relative to config file

this avoids unpredictable path locations when running non-source versions of the watchdog
include support for authenticated smpt sending