Dev doc update

Updated Developer Doc to work for users who don't already have ruby installed.

The ruby bundled with chef can't properly run bundle install for gitlab due to the chef omnibus using an old openssl version, so if ruby isn't available we need to make sure to compile it.

Also added autoconf for the apt-get install, which is required for installing berks, and wasn't included in build-essential on Ubuntu 14.04

#52

See merge request !102

Use superior `postgres::ruby` recipe instead of database_postgresql_pg_gem

When the `external_database` attribute is set to `true`, the `database_postgresql_pg_gem` fails to install the `pg` gem on a vanilla Ubuntu machine because some packages (e.g. `build-essentials`) are not yet installed. The `postgres::ruby` recipe handles this correctly, so just reference that instead.

See merge request !99

Fixed typo

Fixed typo in build-essential package name

See merge request !106

Additional troubleshoot for vagrant installation

See merge request !20

Additional troubleshoot for vagrant

See merge request !104

Add login instructions to vagrant install

See merge request !105

When installing gitlab via vagrant / cookbook pg won't install properly.
Installing the build-essentials package resolved the issue

 * Toggle the compile_ruby flag in /tmp/solo.json based on whether ruby is found in the path
 ** Using chef's embedded ruby isn't going to work properly for this cookbook, so we need to make sure a proper ruby is available
 * Add autoconf to the Ubuntu apt-get install steps, as it doesn't appear to come with build-essential and it is required for the install of berks
 * Remove the troubleshooting section about the PostgresSQL not recognizing new Debian distros, this has been fixed.
 * Updated troubleshooting to point out that chef-solo needs to be run with a newer ruby set on the path

Type in Readme: Change version to 7.1

See merge request !101

MySQL Dependency Fix

I got a load error when I overwrote the below options.
- "external_database": true
- "database_adapter": "mysql"

If external_database is true and using mysql, this processing does not include "database::mysql", so it can't load 'mysql'.

```
LoadError
cannot load such file -- mysql

Cookbook Trace:
/var/lib/aws/opsworks/cache/cookbooks/database/libraries/provider_database_mysql_user.rb:29:in `require'
/var/lib/aws/opsworks/cache/cookbooks/database/libraries/provider_database_mysql_user.rb:29:in `load_current_resource'

Resource Declaration:
 In /var/lib/aws/opsworks/cache/cookbooks/gitlab/recipes/database_mysql.rb
23: mysql_database_user gitlab['database_user'] do
24:   connection mysql_connection
25:   password gitlab['database_password']
26:   host mysql['client_host']
27:   action :create
28: end
29:
```

See merge request !77

Remove custom postgresql fork

The custom fork wasn't working properly for Ubuntu 14.04

Tested on Ubuntu 14.04
Ruby 2.1.2
Chef 11.6.2

bundle exec rspec was run and passed

#30

See merge request !100

Cron to make backups

Add a backup recipe to configure cron to make backups

See merge request !98

Make max upload size configurable

In order to upload large git objects, nginx's `client_max_body_size` and gitlab's `max_size` should be configurable.

See merge request !95

Ldap filter

Added ability to place LDAP filter in the cookbook.  Also added an example of a recursive query for user filtering.

See merge request !94

Removing the cookbook for the custom fork for postgresql. The community cookbook has progressed past this point.