gitolite with non-default port

ssh gitolite
Mot picture Mot · Sep 7, 2011 · Viewed 7k times · Source

To clone a repository managed by gitolite one usually uses following syntax

git clone gitolite@server:repository

This tells the SSH client to connect to port 22 of server using gitolite as user name. When I try it with the port number:

git clone gitolite@server:22:repository

Git complains that the repository 22:repository is not available. What syntax should be used if the SSH server uses a different port?

Answer

Chris Johnsen picture Chris Johnsen · Sep 8, 2011

The “SCP style” Git URL syntax (user@server:path) does not support including a port. To include a port, you must use an ssh:// “Git URL”. For example:

ssh://gitolite@server:2222/repository

Note: As compared to gitolite@server:repository, this presents a slightly different repository path to the remote end (the absolute /repository instead of the relative path repository); Gitolite accepts both types of paths, other systems may vary.

An alternative is to use a Host entry in your ~/.ssh/config (see your ssh_config(5) manpage). With such an entry, you can create an “SSH host nickname” that incorporates the server name/address, the remote user name, and the non-default port number (as well as any other SSH options you might like):

Host gitolite
    User     gitolite
    HostName server
    Port     2222

Then you can use very simple Git URLs like gitolite:repository.

If you have to document (and or configure) this for multiple people, I would go with ssh:// URLs, since there is no extra configuration involved.

If this is just for you (especially if you might end up accessing multiple repositories from the same server), it might be nice to have the SSH host nickname to save some typing.

Related questions

Specify an SSH key for git push for a given domain

I have the following use case: I would like to be able to push to [email protected]:gitolite-admin using the private key of user gitolite-admin, while I want to push to [email protected]:some_repo using …

Read More
GitLab requires git@localhost password to push to a repo

I'm trying to get GitLab up and running on my server. I followed the installation instructions at the gitlab github page and everything went well. The issue is, when I create a repo and try to sudo git push -u …

Read More
Adding users to Gitolite

I'm trying to setup Gitolite but I'm running into a weird issue: When I add a new public key file for a new user (say raphaelcruzeiro.pub), giolite sends me the following warning on push: remote: remote: ***** WARNING ***** remote: the …

Read More