Task: Remove Forgejo & Git-Specific Reverse Proxying (Retain Caddy as Generic Ingress)

Parent

SZ-87 — Replace Forgejo with Internal Sztab-Managed Git (Semi-Production Requirement)

Description

This sub-issue covers the complete removal of Forgejo from the Sztab deployment and the elimination of all Git-specific reverse proxying, while intentionally retaining Caddy as a generic ingress and TLS terminator for Sztab UI and backend services.

The goal of this step is to establish a clean, stable baseline where:

• Git remains a concept inside Sztab
• No Git service is exposed at the ingress layer
• No infrastructure component (Caddy, Docker Compose) has knowledge of Git

This is a deliberate boundary-setting step and a prerequisite for introducing a new Sztab-managed internal Git solution in subsequent work.

Scope

In Scope

• Remove Forgejo service/container from Docker Compose
• Remove Forgejo-related volumes, environment variables, and networks
• Remove all Forgejo-related reverse proxy configuration from Caddy
• Remove Git-specific routing (hostnames, paths such as /git/*)
• Retain Caddy for:
  • Sztab UI
  • Sztab backend
• Verify system starts and functions without Forgejo present

Out of Scope

• Selecting or implementing an internal Git repository
• Exposing Git over HTTP
• Git authentication or user management
• External Git provider integration (GitHub, OneDev, etc.)

Acceptance Criteria

• docker compose up succeeds with no Forgejo service present
• Caddy runs without any Git-specific routing or hostnames
• Sztab UI loads successfully
• Sztab backend APIs respond normally
• No ingress configuration references Forgejo or Git endpoints
• Git remains internal-only and invisible at ingress level

Rationale

This step enforces a clear architectural invariant:

The ingress layer must have zero awareness of Git.

By removing Forgejo and all Git-specific proxying first, we avoid carrying forward authentication, routing, or UX assumptions into the new internal Git design.

This reduces coupling and risk in later steps of SZ-87.

Work Log

•  Identify and remove Forgejo service from docker-compose.yml
•  Remove Forgejo volumes, networks, and environment variables
•  Remove Forgejo-related site blocks from Caddyfile
•  Remove Git-specific reverse proxy paths and routing rules
•  Restart stack and validate UI and backend functionality
•  Verify no Forgejo/Git references remain in ingress configuration
•  Document completion and observations in parent issue SZ-87

Time Estimate

• Estimated: 2.0 hours
• Actual: TBD

Notes

This sub-issue is a prerequisite for:

• SZ-87.2 — Choose & package lightweight internal Git repository
• SZ-87.3 — Devise user-friendly workflow for internal vs external repositories