Type at least two letters to search every page of the docs.

↑ ↓ to navigate ↵ to open esc to close

Using rdev

Git access

Your server clones and pushes your repositories itself, so it needs its own way into GitHub, GitLab, Bitbucket or your own Git server. Public repositories need nothing. For private ones, give the server a key or a token once; every project after that just works.

Keys and tokens stay on your server. rdev.cloud only sees public keys, and a token you type in the panel is encrypted in your browser for your server before it is sent.

Three ways in

Way Reaches Best for
Server key Every repository your Git account can open One personal account
Accounts The repositories of the owners you list, each with its own SSH key or token Several accounts, work and personal, other hosts
Deploy key A single repository The narrowest access, client repositories

When the server clones, it picks the first that fits: the project's deploy key, then an account whose host and owner match the URL, then the server key. If an SSH clone is refused and the repository is public, it falls back to HTTPS. Each clone remembers how it was opened, so git pull and git push keep working.

The server key

Open the server under Servers, go to the Access tab and find Git access. Choose Make key the first time, copy the key and add it to your account: GitHub, GitLab and Bitbucket have a button each that opens the right page. The same key works for pushes, so your AI agent can push too.

From the server's terminal:

rdev git key            # print the key (made on first use)
rdev git key --rotate   # make a new one; remove the old one from your hosts

Accounts

Add as many accounts as you like: two GitHub accounts, a company GitLab, Bitbucket and a self-hosted Gitea side by side. Each account has:

  • Name: short, such as work or personal.
  • Host: github.com, gitlab.com, bitbucket.org or your own, with :port when SSH is not on 22.
  • Owners: optional users or organizations. Repositories under them use this account; with no owners, every repository on the host does.
  • SSH key or token: an SSH account gets its own key to add on the host. A token account clones over HTTPS with a personal access token (GitHub fine-grained token, GitLab personal or project token, Bitbucket API token, Azure DevOps PAT). GitLab expects the user name oauth2, Bitbucket your e-mail.

In the panel choose Add account. In the laptop app the same list is on the Integrations tab. From the terminal:

rdev git account add work --host github.com --owner acme
echo "$TOKEN" | rdev git account add lab --host git.example.com --token --user oauth2
rdev git account list
rdev git account remove lab

Deploy keys

A deploy key opens one repository. Under Deploy keys type the project's name (an existing project or the one you are about to add) and choose Make deploy key, then add the key to the repository's deploy keys, with write access if the agent should push. When you add the project, tick Use the project's deploy key, or run:

rdev git key --project shop
rdev project add shop --git [email protected]:acme/shop.git --deploy-key

Trusting a host

The server already knows the keys of GitHub, GitLab and Bitbucket. The first time it meets another host it does not connect blindly: the host appears under Hosts waiting to be trusted with its fingerprint. Compare it with the one your Git host publishes and choose Trust, or run rdev git trust git.example.com --fingerprint SHA256:….

Testing access

Before adding a project, paste its URL under Test access. The server tries to read it and, if you tick Also check that it may push, to push without changing anything. The answer says which key or token it used, or what to do next. From the terminal: rdev git test <url> [--write].