Also, is_admin and can_create_group are exposed in the user information.
Fixed attributes_for_keys to process properly keys with boolean values (since false.present? is false).

run mysql_secure_installation to secure the freshly installed mysql server

Change-Id: I1bdd3608d3b46924b5da3ae282c99f85ee4e0dab

Change-Id: I1337ee7ff51d018d6f62d447345032597e84269f

need to be in /home/git/gitlab

Corrects the update document to match the version of gitshell specified in the install document (1.7.1)

SSH is pronounced as /es es aged/, so we need "an" instead of "a".

-Specifying a header of SUDO or adding a :sudo with either user id, or username of the user will set the current_user to be that user if your identifying private_token/PRIVATE_TOKEN is an administrator token

Change-Id: I5b174bba02856ede788dcb51ec9b0d598ea7d0df

Satellites for projects that were located in the root namespace needs to be recreated once they've been migrated to the creator’s namespace during the upgrade process.

This can be achieved by running the sudo -u git -H bundle exec rake gitlab:satellites:create RAILS_ENV=production during the update process.

The command has been added to the 5.4 to 6.0 update doc.

Since it is easily could break installations running on the server - hence the person doing the install should be able to make the decision to remove himself.

Use "/commits/:sha/diff" as opposed to "/commit/:sha", keeping in line
with existing api urls (e.g. "/projects/:id", etc.)

Fix 500 error resulting from a diff api call with an invalid commit hash

Move "/commits/:sha/blob" to "/blobs/:sha", leaving the old path for
backwards compatibility.

Add ability to get a single commit via "/commits/:sha"

As a consequence on the namespaces change from 5.4 to 6.0, after upgrade
lots of links on the dashboard were not working (pointing to projects
without the group part on the url).
Also, after upgrading to 6.0-stable, the network (branch history) function
does not work. The progress bar rotates forever, but the network graph cannot
be generated.

Clearing redis cache fixes those issues.

Isn't 5.4 current stable?