GIT REPOSITORY HOSTING
Host Git repositories without another hosting platform.Host Git repositories without another hosting platform.
Keep repository storage in Keldra. Use standard Git over smart HTTP to clone, fetch, pull and push. The first authorised push creates a repository, using your existing Keldra application credentials and bucket permissions.
Your code. Your infrastructure. A repository backend to build on.
HOW IT WORKS
Push. Create. Collaborate.
Point a standard Git client at your repository's HTTP address. Keldra stores the repository so your team can keep using familiar commands.
1
Authenticate and push
Use your application's client ID and secret for an authorised push to the repository path.
2
Repository created
The first authorised push creates the repository. Later pushes update it through the same Git transport.
3
Permissions applied
Application and bucket permissions protect access. Pushes always require authorisation.
4
Clone, fetch, pull and push
Your team works with the repository through standard Git clients.
1
Authenticate and push
Use your application's client ID and secret for an authorised push to the repository path.
2
Repository created
The first authorised push creates the repository. Later pushes update it through the same Git transport.
3
Permissions applied
Application and bucket permissions protect access. Pushes always require authorisation.
4
Clone, fetch, pull and push
Your team works with the repository through standard Git clients.
1
Authenticate and push
Use your application's client ID and secret for an authorised push to the repository path.
2
Repository created
The first authorised push creates the repository. Later pushes update it through the same Git transport.
3
Permissions applied
Application and bucket permissions protect access. Pushes always require authorisation.
4
Clone, fetch, pull and push
Your team works with the repository through standard Git clients.
Use the Git commands you know
Set the URL for your server, tenant, bucket and repository. Run the first push from an existing local repository with a main branch.
export KELDRA_GIT_URL=https://storage.example.com/git/acme/code/app.git
git remote add keldra "$KELDRA_GIT_URL"
git push -u keldra main
git clone "$KELDRA_GIT_URL" app
cd app
git pull
git push
Use your Git credential manager for the application client ID and secret. Do not embed secrets in the repository URL or commit them to Git configuration.
BUILT FOR YOUR OWN WORKFLOW
Repository storage, team access and commit-path lookup.
Use Keldra when you need repository hosting as part of your own infrastructure or product, rather than another complete development platform.
Use your existing storage
Keep Git repository content alongside the files your Keldra deployment already stores. Use private buckets for private repositories, or explicitly enable public reads for public clones.
Build the interface your product needs
Use the Git backend for internal repository hosting or build your own repository interface around it. Your application can provide the workflow and presentation your users need.
Look up commits and tree paths
The GitSource index addresses a configured repository by commit ID and exact or prefix tree path. Locate files at a commit without claiming arbitrary source-text, symbol or AST search.
Use your existing storage
Keep Git repository content alongside the files your Keldra deployment already stores. Use private buckets for private repositories, or explicitly enable public reads for public clones.
Build the interface your product needs
Use the Git backend for internal repository hosting or build your own repository interface around it. Your application can provide the workflow and presentation your users need.
Look up commits and tree paths
The GitSource index addresses a configured repository by commit ID and exact or prefix tree path. Locate files at a commit without claiming arbitrary source-text, symbol or AST search.
Use your existing storage
Keep Git repository content alongside the files your Keldra deployment already stores. Use private buckets for private repositories, or explicitly enable public reads for public clones.
Build the interface your product needs
Use the Git backend for internal repository hosting or build your own repository interface around it. Your application can provide the workflow and presentation your users need.
Look up commits and tree paths
The GitSource index addresses a configured repository by commit ID and exact or prefix tree path. Locate files at a commit without claiming arbitrary source-text, symbol or AST search.
Repository hosting, not a bundled project suite
Git HTTP support does not include issue tracking, pull requests, continuous integration, a browser code editor or SSH transport. Add the product features your workflow actually needs on top of the repository backend.
Keep deployment requirements clear
The optional Git gateway uses the Git executable on the server. Configure and qualify that gateway alongside your Keldra deployment; the public transport is Git smart HTTP.
SELF-HOSTED DEVELOPMENT
Keep your source code on infrastructure you control.
Start with Keldra's object storage setup, then use its Git HTTP gateway for the repositories your team or product needs.