The SSH key object

Remember, on fortrabbit an account represents a person. SSH key authentication is used to securely identify you for your personal code access. SSH keys are an object within the fortrabbit dashboard. Personal SSH keys can be managed with your account settings, deploy keys with each environment.

Don't have local SSH keys already or don't know what that is? See the SSH key setup and intro.

# Adding SSH keys to fortrabbit

The public part of the key must be imported in the fortrabbit dashboard. Paste the public part of the key, not the private part. The value to paste into the text field can be copied to the clipboard.

# macOS
$ pbcopy < ~/.ssh/id_ed25519.pub

# Linux
$ xclip -i < ~/.ssh/id_ed25519.pub

# Windows
# Open the `id_ed25519.pub` file, select all, then copy.

See the SSH key setup guide if you're new to SSH keys.

# Personal keys

In most cases you want to add SSH keys to your personal developer account at fortrabbit to directly login to the environment and opening an SSH tunnel. Personal SSH keys will be automatically added to all the environments you have a developer connection to.

Already using GitHub and our deployment flows? The fortrabbit dashboard may directly import public keys associated with your GitHub account so you don't need to setup additional keys for this.

# Deploy keys

In certain scenarios, you may want to grant a non-human service access to an environment. Use deploy keys for that. The deploy keys are managed via the dashboard with the environments. Adding and removing such keys follows the same concepts as described above. Use deploy keys to integrate with Git hosting services or deploy services.