Isn't 5.4 current stable?

This reverts commit 670e1be7.

This reverts commit b5cd66d4.

Additional unicorn -> puma reference update

Updated incorrect/outdated references to unicorn.rb; changed to puma.rb

I've moved the instruction in question to the the 
'Configure GitLab DB settings'. Can't change permission to a file that doesn't already exist 

Fix spelling error and make sure you never log in as git user so you never have to logout to run sudo.

addresses gitlabhq/gitlabhq#3809

Setting Git's global user.name and user.email are missing from
instructions, causing check.rake to fail at this step.

Signed-off-by: Axilleas Pipinellis <axilleas@archlinux.gr>

Signed-off-by: Axilleas Pipinellis <axilleas@archlinux.gr>

By default there is no public/uploads directory when no attachments
are uploaded. Prompt users to create the uploads directory during
install otherwise the backup task will fail.

Place mysqldump args in single quotes to avoid error if password
contains special characters.

Signed-off-by: Axilleas Pipinellis <axilleas@archlinux.gr>

For some reason, if the nginx configuration is bound to an IP, it breaks the install, causing all git clone/push/pull operations to die with a 'fatal: The remote end hung up unexpectedly' message. Changing this configuration seems to fix the problem. I reckon that this is just a temporary fix. I don't know the ins and outs of GitLab well enough to vouch for this change, but I do know that these instructions are broken, and that this update will fix them.