Seems to require absolute path in remote

[anamba]

Relative paths in the remote specification (i.e. starting from $HOME) should be left unharmed. Currently, git deploy setup appears to add a '/' before the path, which will break any relative path.

[Struki84]

I see the need to force absolute paths, but then maybe it would be good thing to handle the error. The script breaks apart because mk dir returns "you do not have premissions". Usually that mistake means your not pointing the right folder. Also what happens if you do have permissions and he creates the repo in the wrong place?

[stefanotorresi]

I'm also experiencing this problem. Having a remote like user@host:directory/repo should mean repo is deployed into $HOME/directory, not /directory.

[mislav]

I agree that relative paths should not be transformed into absolute. Does anyone want to take a stab at a pull request?