Skip to content
Gittensory
Self-hosting

Releases and images

How to consume official self-host images, pin versions, build custom images, and keep source maps aligned.

Image tags

version
Pinned release tag. Use this in production.
latest
Moves with the newest STABLE release only — never a prerelease. Useful for trials, not for controlled production.
sha
Immutable commit-derived tag for exact provenance and rollback.
docker pull ghcr.io/jsonbored/gittensory-selfhost:orb-v0.1.0
docker pull ghcr.io/jsonbored/gittensory-selfhost:latest
bash

Prerelease (beta/rc) images

A tag like orb-v0.1.0-rc.1 or orb-v0.1.0-beta.1 runs the identical build/provenance/SBOM/Sentry pipeline as a stable release, but is marked prerelease on GitHub and is never pushed under latest. External beta testers should pull the exact prerelease tag, not latest.

docker pull ghcr.io/jsonbored/gittensory-selfhost:orb-v0.1.0-rc.1
bash
Stable release behavior is unchanged: a plain X.Y.Z tag still moves latest and publishes an unmarked (non-prerelease) GitHub Release.
Before tagging any orb-v* release or prerelease, run the beta release checklist against the built image — CI only smoke-tests the plain SQLite + Redis + direct-App default, not brokered mode, air-gapped mode, or any AI provider.

Upgrade flow

  1. Read release notes for env, migration, or behavior changes.
  2. Back up the database or confirm Litestream health.
  3. Pull the new image tag.
  4. Recreate the app container.
  5. Check /ready, logs, queue metrics, and one test PR.
docker compose pull gittensory
docker compose up -d gittensory
curl http://localhost:8787/ready
bash

Custom images

Custom builds are useful for testing local changes or including subscription CLIs. They should not contain secrets.

docker compose build --build-arg INSTALL_AI_CLIS=true gittensory
docker compose up -d gittensory
bash

Sentry source maps

Official releases align GITTENSORY_VERSION, Sentry release ids, and uploaded source maps. For custom images, leave SENTRY_RELEASE unset unless you uploaded source maps for that exact built bundle.

Rollback

Roll back by pinning the prior image tag and recreating the container. Database migrations can make rollback harder, so keep backups and read release notes before upgrading a live maintainer instance.

← PreviousTroubleshootingNext →Beta release checklist