Files
GitManager/.env.example
T
TBNilles 32ae17cc9f Config: .env = projects root only; derive each project's forge from git
Reduce .env to just REPOS_HOST_PATH (the projects root); runtime bootstrap moves to compose/defaults. Projects are the subdirectories of the single root — removed the project-directories feature (store table, service methods, /api/config/project-dirs, Settings section). Each project's forge is derived from its git remote (matched to a configured forge, else the bare host) and shown as a pill next to its name (State.Forge via scanner ForgeFor + svc.ForgeDisplay). Removed first-run .env seeding; forges + identity are managed in Settings. Added forge.HostOf. AGENT.md updated.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-09-22 05:52:03 -04:00

16 lines
910 B
Bash

# ---------------------------------------------------------------------------
# GitManager configuration. Copy this file to `.env`.
# NEVER commit a real `.env` (it is git-ignored).
#
# The ONLY thing configured in .env is the root directory that holds your
# projects. Each project is a subdirectory of that root, and its forge is
# detected from its git remote. Everything else — forge hosts + access tokens
# and the git commit identity — is managed in the app's Settings (/settings) and
# stored in a private database (AGENT.md §1.5). Runtime bootstrap (listen address,
# TLS, DB path, the container projects root) is set by docker-compose.
# ---------------------------------------------------------------------------
# Host folder that holds your projects. docker-compose mounts it to /repos inside
# the container (scanned as PROJECTS_ROOT). Example: C:/Users/you/Projects
REPOS_HOST_PATH=./repos