Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

It seems there is no easy way to count pattern occurences with
String#match.

If you are running another sidekiq instance on your server, e.g. GitLab
CI, the check script would parse the output of `ps aux` searching for
`sidekiq` and returning success, although the GitLab sidekiq may not be
running.

Now the `ps` call will only print the processes run by the GitLab user.

We sometimes encounter connectivity issues where gitlab-shell cannot
make API calls to the Rails application. There is a self-test script
`gitlab-shell/bin/check` that tries to connect to the API; this commit
runs that script as part of `rake gitlab:check`.

* GitLab Shell 1.7.1 is required
* Global projects are not supported (refs #5152)

Use gitlab-shell authorized_keys truncation. Fix issue with authorized_keys stored in different location

When the file that pointed git bin_path in gitlab.yml dose'nt exist,
bundle rake gitlab:app:check would be aborted.

refs #4205

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

e.g.: the sidekiq in my Debian box is v2.11.1

It returns "yes" if required version is "1.7.10" and current version is "1.6.10",
because the patch version of current version equals to that of required version.

Checking is "yes" only if git version equals "1.7.10" exactly.

Checking the redis version will warn users that
are using an old version to update. Included
reference to the troubleshooting guide.

Checking the redis version will warn users that
are using an old version to update. Included
reference to the troubleshooting guide.

Fixing issue #2970