Don't start gitlab service until pids/ has been created

Sometimes the gitlab service will not start on the first provision. It works on the second attempt though.

Puma writes to /home/git/gitlab/tmp/pids/puma.pid. If pids/ doesn't exist, it fails silently. The order in which server.pp is run seems to cause the differing behaviour on fresh VMs.
Merge pull request #58 from achaphiv/patch-1

Don't start gitlab service until pids/ has been created
Trigger nginx to restart after config added

Related to #54 and #56.

Gitlab does not start up on the first provision because nginx does not actually watch /etc/nginx/conf.d/. By default it watches /tmp/nginx.d/.

I thought about putting the file in /tmp/nginx.d/, but that location is configurable, so this commit instead just notifies the service directly.
Merge pull request #59 from achaphiv/patch-2

Trigger nginx to restart after config added
[server] Lint recipe

 * WARNING: double quoted string containing no variables on line 212
 * ERROR: two-space soft tabs not used on line 199
[rake] Add puppet-lint task (disable 80char warn)
[pre] Add python-docutils (additional package of 6.0)
[init] Use gitlab_branch var for redhat warning
[params] Switch to gitlab 6.0-stable and gitlab-shell v1.7.0
[templates] Update gitlab/unicorn/init templates for 6.0
[server] Re-re switch from puma to unicorn :-)
write nginx vhost config only when using nginx
[params] Fix gitlab branch name s/./-
update readme for gitlab 6.0