01 / PLACEMENT

Start small. Keep ownership clear.

Both profiles run the portable core.

Local / Docker Compose

The standard Compose stack serves Golf on localhost:8080 and Forgejo on localhost:3001. Persistent volumes and generated private configuration survive ordinary stop/start and down without volume removal.

Docker execution

Explicitly enroll workers, initialize private object storage and authorize accepted workflows. Optional agent accounts and execution policies have their own setup and qualification.

Kubernetes / Helm

Supply your built image, existing namespace Secret, public origins, storage and enforcing network policy. The core chart supports external dependencies; it does not install every execution subsystem.

Portable source, collaboration and optional execution ownership.
Portable source, collaboration and optional execution ownership. Mermaid source ↗
02 / OPERATE DELIBERATELY

Fresh installs use Forgejo.

No in-place database swap

The Forgejo transition uses a fresh target and explicit identity/data fidelity checks. A rehearsal lost a private pending review; retained cutover remains blocked.

Recovery is provider-specific

The historical recovery tool qualified a bounded earlier provider profile. It does not qualify current Forgejo backup/restore or Kubernetes disaster recovery.

Selective Cloudflare adoption

Portable installations may choose supported optional storage or provider adapters. Choosing one integration does not turn the portable core into the complete native SaaS stack.

Make your first move.

Explore the hosted public repository, request enrollment for private workflows, or start your own portable installation.

Find your next step

31 pages and guides

Tab through results · Enter to open · Escape to close