Codebase repositories are added to DeployHQ manually - the same way we currently support Gitea, Forgejo, or any Git hosting platform. Git and Mercurial repositories connect over SSH using a deployment key, while Subversion repositories connect over HTTPS with a username and password.

When you first create your project, in the **Where is your repository hosted?** area, tick **Add your repository details manually?**:

{screenshot: 19}

## Git and Mercurial repositories

Enter the full SSH URL to your Codebase repository, a custom port if one is required, and the default branch you wish to deploy from. Your Codebase SSH URL looks something like this:

`git@codebasehq.com:account/project/repository.git`

You can view your project's public key on this screen. You'll need to add this key to your Codebase repository so that DeployHQ can access it:

1. In Codebase, navigate to your repository's **Settings**, then the **Deployment Keys** tab.
2. Click **Add new SSH public key**, give the key a name, paste in your DeployHQ project's public key, and click **Add Public Key**.

{screenshot: 91}

Full steps for adding the deployment key are covered in [Uploading your project's public key to Codebase manually](Article: #135).

## Subversion repositories

Subversion repositories are added over HTTPS rather than SSH. Enter the full HTTPS URL to your Codebase repository along with the username and password you use to access it - there's no deployment key to add.

Once the repository details are saved, DeployHQ will be able to connect to your repository and cache it ready for deployment. You can also set up automatic deployments so a push to Codebase triggers a deployment - see [How to automatically deploy a Codebase repository](Article: #151).