Use one Procfile and bootstrap during 'make'

Depends on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2429

See merge request !98

Increase min memory of vagrant to 3GB to fix out-of-memory errors on dev:setup

The command `~/gitlab-development-kit/gitlab$ bundle exec rake dev:setup`
fails with an out of memory error. Increase the min memory configured in
the Vagrant virtual machine from 2GB to 3GB.

addresses #48

See merge request !66

If the bootstrap script fails, Make will delete the file it was trying
to 'build'. In this case that meant deleted PG_VERSION. By make a
directory, postgresql/data, instead of a file the target we prevent
this deleting behavior.

We want this because the bootstrap can take forever while it generates
seed data and the user may press Ctrl-C.

Change phantomjs requirement to 192 for OS X installs. Fixes #79



See merge request !99

cc @brodock

Simple pg replication setup tasks on Makefile

I've documented on the Makefile some steps I used to make a working postgres replication master/slave on my local machine.

This is something that will help anyone working with GitLab Geo in the future: https://gitlab.com/gitlab-org/gitlab-ee/issues/76

This still not perfect, so I would like some help from anyone who can automate it better then I do.

Current Caveats:
* I got it working correctly only with a clean postgres install

How to use it:
1. `rm -rf postgresql`
2. `make postgresql`
3. `make postgresql-replication/cluster`
4. `foreman start postgresql`
5. `make postgresql-replication/role`
6. `make postgresql-replication/backup`
7. ~~add replication user data to pg_hba on `postgresql/data/pg_hba.conf`~~ (automated)
8. stop foreman and start it normally with `foreman start` and then bootstrap gitlab database as always

pg_hba data:
```
host    replication     gitlab_replication        127.0.0.1/32            trust
host    replication     gitlab_replication        ::1/128                 trust
```

cc @marin @jacobvosmaer

See merge request !96

apt-add-repository is missing on docker

but used in Vagrantfile from some point

And adding rsync to save vagrant execution time
(vagrant tries to install it)

See merge request !95

but used in Vagrantfile from some point

+ Adding rsync to save vagrant execution time
(vagrant tries to install it)

Add option to update gitlab-workhorse

Already tested on my kit :)

See merge request !91

Stash any uncommitted changes before pulling



See merge request !83

Fedora in install instructions



See merge request !85

Install dependencies from package

Some more improvements to the Vagrantfile and documentation.

* Install RVM from their PPA
* Install Recent Go from Ubuntu-LXC PPA

See merge request !90

Disable NFS on OS X and Fix issue with initdb

Syncing GDK folder using rsync instead of vagrant default share, will fix #46.

Disabling NFS on OS X will make sure we don't have incorrect UID/GID on guest machine, as described on #68.

See merge request !89

Recent Go is published from the Ubuntu LXC PPA
RVM PPA is from official contributor

Update README to include bundle install for dev kit itself

Currently the `README` doesn't mention the fact that you need to run `bundle install` on the dev kit to get foreman etc.

WRT markdown style guide - I've gone for the 80 char width option because I write python usually  There already seems to be a mixture in this file, so I guess thats not too important so long as it renders correctly?

See merge request !87

Elaborate on post-installation instructions

To ensure there is clarity in the user's mind concerning what processes they are setting up and what ports they can expect to find a service.

See merge request !82

Fix-up items missed by !79 for #63

I forgot to search and replace the old section "Install Gems and Repositories" mentions in the other sections in the previous MR.

See merge request !80