add a ``bin/deploy`` console script and a first stab at a freebsd ezjailremote wrapper
provide defaults for configuration values
configure ZFS setup, install ezjail into it and create a basic appserver jail
configure ntp (TODO: also configure ntpd)
install ezjail with ports

this way we can build the required packages from source instead of
trusting pre-built binaries.
document the deployment strategy
consolidate verision info

this config is the only place where it is used, anyway.
rename deploymnent.cfg to zeitonline.cfg, move appserver to top

deployment has become ambiguous since we now address several aspects of
it separately (i.e. the webserver, the appserver, the jailhost etc.)

also, since each buildout configuration is now self-contained (i.e.
everything needed for running the appserver lives inside appserver.cfg
there is no longer a need to 'hide' the individual config files inside a
separate buildout directory.

now each top-level .cfg is self-contained and the deployment.cfg is free
to be used for setting up the deployment scripts.
use deployment.cfg for, well... deploying the stack :-)
a folder with one file makes no sense :)
text cosmetics
restructure for easier debugging

this way it's easier to temporarily disable parts that have already run
upload port configuration and install ports for appserver
bugfix: move to config, where the template expects it
configure and update the appserver.

TODO: still need to configure and start supervisor
bugfix: we need to actually install libxslt, not just configure its port
allow to select which deployment steps are run from the CLI
use supervisor from the bsd ports to start up and control the app
don't run bootstrap if we're only updating
remove fluff