Your Code. Your Rules.

Access over SSH

Clone, pull, and push git repositories over SSH with an Ed25519 or RSA-2048+ key registered on your git.eu account.

Access over SSH

Clone, pull, and push over SSH with a key pair - no password, no token in the URL. Keys: Ed25519 (recommended) or RSA of at least 2048 bits; ECDSA, DSA, and smaller RSA keys are rejected.


Step 1 - Generate a Key Pair

Generate an Ed25519 key pair, accept the default location (~/.ssh/id_ed25519):

ssh-keygen -t ed25519

Set a passphrase when prompted - a lost laptop then does not expose the key.

Prefer RSA? Use a modulus of at least 2048 bits:

ssh-keygen -t rsa -b 4096

Step 2 - Add the Public Key to Your Account

Copy the full contents of the public file (~/.ssh/id_ed25519.pub) into Settings → Git Access → SSH Keys, with a name per device (for example my-laptop):

cat ~/.ssh/id_ed25519.pub

Step 3 - Clone, Pull, and Push

Create the repository on your instance first (web UI: New repository), then clone it:

git clone git@<INSTANCE>.git.eu:<USERNAME>/REPO_NAME.git
cd REPO_NAME

Already have a working copy over HTTPS? Switch the remote:

git remote set-url origin git@<INSTANCE>.git.eu:<USERNAME>/REPO_NAME.git

Then work as usual - git add, git commit, git pull, git push.

Large files? Git LFS works with an SSH remote too - see Git LFS.


Troubleshooting

Every other SSH error, with its fix: Knowledge Base - SSH.


About

The private key never leaves your machine; git.eu only stores the public half. <INSTANCE> (your instance slug, for example beta2) and <USERNAME> (your account name) resolve automatically in commands and buttons when you are signed in on this site; otherwise swap them for your own values.


Next Steps

Ready to get started?

Manage your SSH keys