Connectors
Git
Self-hosted Git for Octo Cloud apps: where a space's repositories live, how to sign in, what the agent does with code, and how to take the source with you.
Last updated:
On this page
What it is
The code of the apps the agent builds and deploys to Octo Cloud lives on our Git host git.octodus.com (Forgejo). Each space has its own organization there; the app repositories in it are private.
- The space's organization and service account are created together with the space.
- An app repository appears on the first deploy, the first commit, or when the agent creates it at your request.
What the agent does
- Creates repositories, commits and pushes, and works with issues and pull requests.
- Deploys the app from the repository: the repository stays the source of truth.
- Reads CI build logs.
Access and on whose behalf
The agent works with Git as its space's service account (svc-<space>) and sees only the repositories of that space's organization. You sign in to the Git host with your own dashboard account.
To let one space's agent work with another space's repository, add that space's service account as a collaborator on the repository.
Signing in and cloning
- Open git.octodus.com and sign in through the dashboard: no separate password is needed, and the account is created on first sign-in.
- The space owner becomes an admin of the space's organization once an app repository exists in it.
- Clone the repository over HTTPS:
bash
git clone https://git.octodus.com/<space-org>/<app>.gitThe source stays yours
- On the Apps page of the dashboard you can download any app's code as a zip archive.
- When an app is deleted or stopped for an empty balance, the repository is kept and handed to the owner.
Troubleshooting
- I cannot see the space's repositories
- A repository appears after the first deploy or commit. Sign in to the Git host with the same account as the dashboard.
- Changes did not deploy after a push
- Deploys are done by the agent. Ask it to deploy the app from the repository.