ProjectLocker supports Git over HTTPS as well as SSH. Over HTTPS, you can get your URL by doing the following:
You should see a window like the following:
The above example is for account PLScreencast, project GitCreateDemo, which lives on server 2. You can substitute your account name, project name, and server accordingly.
Over SSH, Git requires public key access. Your public key must be installed with ProjectLocker in order for you to receive access. In order to install your public key:
In a few moments, your key will be posted to the Git server.
Git uses public key authentication to access your repository. If you are being asked for a password, it means that your public key isn't communicating properly. To connect to Git for the first time, do the following:
Mac OS X / Linux
HostName [replace with your ProjectLocker server, e.g. pl2.projectlocker.com]
User [replace with "git-", followed by your account name, e.g. "git-myaccount", NOT your individual ProjectLocker login]
IdentityFile ~/.ssh/[replace with name of key you just created]
Host projectlockerThis tells your computer to use your ProjectLocker key when communicating with ProjectLocker, even if it uses other keys for other servers.
We recommend msysgit as a straightforward client, but we also have instructions for the following clients:
Windows users who use PuTTY already and manage public keys there can take the public key generated by PuttyGen, using the text shown in the "public key for pasting into OpenSSH Authorized_keys file" section.
You may need to attempt to SSH to the box once to accept the host key (the other tools don't present the host key), but just close the app after accepting the key.
Also, be sure to set GIT_SSH to your Plink installation's location. If your key is installed at ProjectLocker, Plink is your GIT_SSH, and Pageant is running, you should be able to use your PuTTY public key. We recommend msysgit's solution though, unless you have a specific reason to use PuTTY keys.
If your keys don't work, make sure that you copied the true full text of the key, including the ssh-rsa or ssh-dss prefix and the user@host postfix.
If you have followed these steps exactly and cannot access your repository, please include a copy of the following command in your Support Request:
This will help us debug what may be going on with your connection. If you see lines something like
debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/[YOUR USER NAME]/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Offering RSA public key: /Users/[YOUR USER NAME]/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply
near the bottom, it means that your public key is not configured correctly on our server and that you should verify that the user has the correct public key added. If you look at which private keys are being offered and don't see any familiar locations, it means your SSH client isn't looking for your keys where you put them and you should either create new ones or ensure that it looks in the right place.
If you're sure your keys are set up correctly, the only thing left to check is that you are a member of the project. If you're an admin, you can add yourself to the project. If not, have an admin do it for you. If you aren't a member of the project, your key won't be made available to it and you'll get connection errors.