Connect with SSH

SSH is the way most people push to Gitza. A key pair on your machine identifies you, nothing is typed on each push, and it keeps working when you turn on two-factor authentication.

Generate a key

If you already have one at ~/.ssh/id_ed25519.pub, skip this step and reuse it.


ssh-keygen -t ed25519 -C "you@example.co.za"

Accept the default location and choose a passphrase. Ed25519 is the current default on every platform; RSA keys of 3072 bits or more also work.

Add the public key to Gitza

Copy the public half, the file that ends in .pub:


cat ~/.ssh/id_ed25519.pub

Then open Settings → SSH / GPG Keys, click Add Key, paste it in and give it a name that tells you which machine it belongs to. Gitza shows the key’s fingerprint once it is saved, which you can compare against ssh-keygen -lf ~/.ssh/id_ed25519.pub.

Check it works


ssh -T git@git.gitza.co.za

The first time, SSH asks you to confirm the server’s host key. After that you should see a line greeting you by username. If you are asked for a password, the key was not offered: check that ssh-add -l lists it, or add an entry to ~/.ssh/config:


Host git.gitza.co.za
  User git
  IdentityFile ~/.ssh/id_ed25519
  IdentitiesOnly yes

The remote address

An SSH remote on Gitza looks like this:


git@git.gitza.co.za:you/your-repo.git

Every repository page shows its own address under the Code button, with SSH and HTTPS side by side.

A key added under Settings belongs to your account and can push to everything you have write access to. To give a server or a deployment job read access to one repository only, add a deploy key in that repository’s Settings → Deploy Keys instead.