Vetrix Docs

Repositories

Git storage and repository lifecycle on a self-hosted instance. These pages cover the bare repositories on disk and the space they consume, replication to and from remote hosts, and the administrative moves that change which account a repository belongs to. They deal with repositories as instance-level objects an operator provisions, replicates, relocates, and reclaims — not with the branch, review, and permission workflows a repository's own members use.

Pages

  • Git Storage — The on-disk layout under git.repo_root (one bare <owner>/<repo>.git per repository) alongside the blob directory for CI artifacts and registry files, the [git] and [storage] configuration keys, reading disk headroom from the admin health endpoint and the thresholds at which Git operations start to fail, periodic repository garbage collection, snapshot and rsync backup strategies with a per-path criticality table, importing an external repository by mirror push, and the .trash/ holding area a deleted repository sits in before permanent removal.
  • Mirror Configuration — The instance-wide mirror.* settings that cap mirrors per repository and floor the sync interval, the in-process scheduler that polls for due pull mirrors and serializes fetches per repository, AES-256-GCM encryption of mirror credentials under MIRROR_ENC_KEY including the boot behaviour when the key is absent and the migration path for deployments whose credentials were sealed under an all-zero key, disk cost of mirrored refs, and how to find, resume, and instance-wide disable mirrors after repeated sync failures.
  • Repository Transfer — The four-phase orchestrator that forcibly reassigns repository ownership — prepare with its name-confirmation gate, preflight and backup manifest, the execute transaction that renames the bare repository and flips the database rows while dropping existing collaborator and group grants, verification, and finalize — together with the prerequisites (including the master switch whose off state makes the endpoints answer as if the feature did not exist), the documented failure classes, and the manual reconciliation procedure for the one-way state a transfer lands in when verification fails after execution.