Configure your storage

Where your data lives

On orbitgit.com, every account must configure its own storage. Git objects and release artifacts use that account’s location. Platform metadata is kept separately; the system bucket is not shared customer repository storage.

Open My storage, save the profile, and check the displayed backend and location. Credentials are saved encrypted.

S3-compatible buckets

1. Create a bucket with Cloudflare R2, AWS S3, Hetzner Object Storage, or another compatible provider.
2. Create credentials allowed to read, write, list, and delete objects in the selected bucket or prefix.
3. Choose S3-compatible in My storage. Enter the API endpoint, bucket, access key, secret key, region, and optional prefix. R2 normally uses region auto.
4. Save, create a small repository, and push to verify access.

Use the S3 API endpoint, not the bucket’s public website or provider dashboard URL.

WebDAV and SFTP

WebDAV needs an HTTPS URL, username, password, and optional root folder. SFTP needs a host, port, username, password or private key, and root folder. The selected deployment must support the backend’s network connection; check with your host if it cannot connect.

Changing credentials or location

Rotate credentials for the same location when needed. Moving or removing a location is blocked while repositories use it. Changing a setting does not migrate Git objects or artifacts; plan a migration first.

Self-hosted operators can configure global storage later, with repository folders separated by owner and name. This deployment option does not grant users access to each other’s repositories.

Troubleshooting

“Configure your own storage” means the account has no usable profile. For access-denied errors, check bucket credentials and prefix permissions. Verify the endpoint, bucket name, TLS connectivity, and provider policy.