# Dev-only overlay: local gitea for git-sync reproduction scenarios.

# Usage:

# docker compose -f docker-compose.yml -f docker-compose.gitea.yml up -d

#

# Pairs with the TRINITY_GIT_BASE_URL env override and the scripts in

# tests/integration/git_sync/. Not intended for production.

services:

gitea:

image: gitea/gitea:1.22-rootless

container_name: trinity-gitea-dev

restart: unless-stopped

ports:

- "3001:3000" # avoids collisions with common dev ports (3000 is often node/web)

environment:

- GITEA__database__DB_TYPE=sqlite3

- GITEA__server__DOMAIN=trinity-gitea-dev

- GITEA__server__ROOT_URL=http://trinity-gitea-dev:3000/

- GITEA__server__SSH_DOMAIN=trinity-gitea-dev

- GITEA__security__INSTALL_LOCK=true

- GITEA__security__SECRET_KEY=dev-secret-not-for-prod

- GITEA__log__MODE=console

- GITEA__log__LEVEL=info

- GITEA__service__DISABLE_REGISTRATION=false

- GITEA__service__REQUIRE_SIGNIN_VIEW=false

volumes:

- gitea-data:/var/lib/gitea

- gitea-config:/etc/gitea

networks:

- trinity-agent-network

labels:

- "trinity.platform=dev-infra"

- "trinity.service=gitea"

# Expose TRINITY_GIT_BASE_URL to the backend so new agents target gitea.

# NB: the patch to git_service.py/startup.sh reads this; without the patch

# this env var is inert.

backend:

environment:

- TRINITY_GIT_BASE_URL=${TRINITY_GIT_BASE_URL:-http://trinity-gitea-dev:3000}

- TRINITY_GIT_API_BASE=${TRINITY_GIT_API_BASE:-http://trinity-gitea-dev:3000/api/v1}

# Override GITHUB_PAT with gitea PAT for the repro harness

- GITHUB_PAT=${GITEA_PAT}

volumes:

gitea-data:

gitea-config: