When bin/create-hooks is run against a live GitLab server, there is
a possibility of race conditions when a user deletes one of their
repositories after bin/create-hooks found it. With this change,
bin/create-hooks will ignore missing file errors.

Conflicts:
	CHANGELOG

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

Fix repository name/path extraction for GitlabUpdate

See merge request !34

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

Update README Markdown style to match CONTRIBUTING

Adding support+tests for annotated tags.

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

Use simplecov for development.

GitlabUpdate: use stripped path for repo_name

Improve coverage.

Use a default for gitlab_url that usually works

This default lets gitlab-shell connect to Unicorn directly, instead of
going through Nginx. This has the following benefits:

- the majority of users no longer has to edit the `gitlab_url`;
- avoid issues when the external GitLab web address does not resolve on
  the GitLab server itself;
- avoid SSL certificate issues.

See merge request !32

Expliclity require 'timeout' from the stdlib

This avoids getting the following error on some platforms:

NameError: uninitialized constant GitlabKeys::Timeout

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

Use lock file when add new entries to authorized_keys

Fixes #21

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

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

Lock file location

Authorized keys lock

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

This prevents concurrent modification of authorized_keys file
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Fix spec failure in Ruby 1.9.3

Before this change, tests in gitlab_projects_spec were passing on Ruby
2.0.0 but not on 1.9.3.

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

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