Basically the issue is that 'gitlab-shell rm-key key-2' removes all keys that match "key-2" pattern.
"key-20", "key-25", etc.
This change makes the regex used in the sed command more strict.

https can be served also on non-standard port

Added configuration options for custom redis servers as well as bin locations

Fix permissions for SSH with StricModes onn

add fork_project command

Change-Id: I0c343c03ee3f033641f9958030ac57d92296547d

Change-Id: I1b3d64d79187c414e326928a96427d1cc6176224

Change-Id: Ia48a93ccbfea6fdc0791ce25cf3e6291bfe7fa08

Refactored update hook as well as fixed a typo. GitlabConfig is now only called once in the update hook.

Added socket support to redis configuration directive per drf's request at https://github.com/gitlabhq/gitlab-shell/pull/35

I've installed following the instructions on Fedora 18, and would be nice to leave the permissions nicely for
SSH daemons configured with StrictModes On (cause u can get as I got this... http://www.daveperrett.com/articles/2010/09/14/ssh-authentication-refused/)

Cheers!

Added fallback to default to localhost if the redis configuration block is missing or empty in config.yml

Update CHANGELOG

Improve gitlab_shell spec and replace `system()` with `exec()`

Do not fall on discover deployment keys. Closes #25

Require openssl

Fix the "uninitialized constant GitlabNet::OpenSSL (NameError)"
after upgrading to ruby 2.0

http_settings configuration option added.

Now it supports:

 * self_signed_cert option to allow self-signed certificates over https protocol.
 * user and password options to pass though http auth.

gitlab_net#host: slash is missing

This also randomizes the key_id used in the tests.

We don't need to keep the ruby process around once we've
established that it's ok to run a git command.

* Used mocks to test if methods are colled
* Increased coverage
* Removed duplication and excess verbage