Getting started

SSH keys

With an SSH key, git recognizes you without passwords or tokens. You create a key pair on your computer: the private key stays there, the public key is registered with Lumbung.

1. Check for an existing key

ls ~/.ssh/id_ed25519.pub

Found one? Skip to step 3.

2. Create a new key

macOS, Linux, and Windows (PowerShell / Git Bash) โ€” the same command:

ssh-keygen -t ed25519 -C "kamu@contoh.id"

Press Enter for the default location. A passphrase is strongly recommended; on macOS store it in Keychain so you're not asked every time:

ssh-add --apple-use-keychain ~/.ssh/id_ed25519

Lumbung accepts ed25519, ecdsa, security keys (sk-โ€ฆ), and RSA of at least 2048 bits. DSA is rejected.

3. Register the public key

Copy the public key:

# macOS
pbcopy < ~/.ssh/id_ed25519.pub
# Linux
cat ~/.ssh/id_ed25519.pub
# Windows (PowerShell)
Get-Content $env:USERPROFILE\.ssh\id_ed25519.pub | Set-Clipboard

Open SSH keys, paste it, add a title, then Add key. Lumbung shows its SHA256:โ€ฆ fingerprint โ€” the same as ssh-keygen -lf ~/.ssh/id_ed25519.pub.

4. Test the connection

ssh -T git@jianren.cloud

It works when you see the greeting Halo @nickname! Kamu terotentikasi ke Lumbung, tetapi tidak ada akses shell. ("Hello โ€” you're authenticated, but there's no shell access").

5. Clone over SSH

git clone git@jianren.cloud:ruang-nama/nama-repo.git

A repo cloned over HTTPS can be switched:

git remote set-url origin git@jianren.cloud:ruang-nama/nama-repo.git

Multiple keys / accounts

Using a separate key for Lumbung? Configure ~/.ssh/config:

Host jianren.cloud
  User git
  IdentityFile ~/.ssh/id_lumbung
  IdentitiesOnly yes

If it fails

  • Permission denied (publickey) โ€” the public key isn't registered, or SSH offers a different key. Run ssh -vT git@jianren.cloud and check the Offering public key lines.
  • Unknown key / connection closed immediately โ€” the key expired or was deleted.
  • No SSH tab in the Clone menu? The admin hasn't enabled SSH on this server yet; use HTTPS + token.