Git over HTTPS and SSH
Every repository on Arkiviva can be cloned and pushed over HTTPS and over SSH. When you are signed in, a repository’s page shows both addresses.
Addresses
For the repository REPOSITORY of the account or Organization OWNER:
| Over | Address |
|---|---|
| HTTPS | https://arkiviva.com/OWNER/REPOSITORY.git |
| SSH | ssh://git@arkiviva.com:2222/OWNER/REPOSITORY.git |
SSH uses port 2222, which is why the SSH address names its port.
git clone https://arkiviva.com/OWNER/REPOSITORY.gitA push does not create a repository. Create it on arkiviva.com first, then push to it.
Signing in over HTTPS
Cloning a public repository needs no sign-in. For a private repository, and for every push, Git asks for a user name and a password:
- the user name is your Arkiviva user name;
- as the password, use an access token.
To create an access token, open your user settings, choose Applications, then New access token. Give the token a name, choose which repositories it may reach, set repository to Read and write (or to Read, if you only clone), and choose Generate token. Copy the token at once: it is not shown again.
Your account password works as well, but only while your account has neither two-factor authentication nor a security key. With either of them, Git over HTTPS needs an access token.
Signing in over SSH
Add your public SSH key to your account: open your user settings, choose SSH / GPG keys, then Add key, and
paste the contents of your public key file, the one whose name ends in .pub. Arkiviva accepts Ed25519 and ECDSA
keys, also those kept on a security key, and RSA keys of 3072 bits or more.
The user name in the SSH address is always git: Arkiviva knows you by your key.
Storage
What you push counts against the storage of the repository’s owner, and so do Git LFS files. When that storage is full, a push that adds commits is refused. Storage says what counts and how to free space.