Use correct user for sysvinit example
Start alaveteli in production mode in sysvinit

Unlikely to want to use sysvinit in the current development setup, so
default to starting in production mode for users who just copy this file
on install.
Use default port for thin

No reason to use non-default
Update how thin starts and stops

Use long form options for clarity
Use thin’s built in start and stop mechanisms
Use thin’s built in process owner options
Bind to localhost only
Use thin’s built in restart command
Fix sysvinit case indentation
Exit gracefully from sysVinit if thin not available

> These scripts should not fail obscurely when the configuration files
> remain but the package has been removed, as configuration files remain
> on the system after the package has been removed. Only when dpkg is
> executed with the --purge option will configuration files be removed.
> In particular, as the /etc/init.d/package script itself is usually a
> conffile, it will remain on the system if the package is removed but
> not purged. Therefore, you should include a test statement at the top
> of the script, like this:
>
>    test -f program-executed-later-in-script || exit 0

https://www.debian.org/doc/debian-policy/ch-opersys.html#s-writing-init
Update sysvinit SITE_HOME, mute thin, etc

- Use $NAME in $SITE_HOME for future daemon name change
- Mute thin output
- Return true from daemon commands
Convert sysvinit-example to ugly
Let ugly generate the full path to the app

Usage of the  $vhost_dir and $vcspath is enough to get the full
path to the app without making the assumption that the app is in
a directory named ‘alaveteli’
Update thin sysvinit descriptions

Replace "web server" with the slightly more correct "app server"
Generate sysvinit with rake task

Now uses ugly so convert it with the rake task
Tidy config_files:convert_init_script
Merge branch 'sysvinit-example' into rails-3-develop