01 / PREREQUISITES

Bring Git, Docker and OpenSSL.

You need private product-repository access. Docker supplies the application build toolchains; no AI or Cloudflare account is needed.

LOCAL TERMINAL
git clone git@github.com:mjtechguy/golf-git.git
cd golf-git
./scripts/init-env.sh
docker compose up -d --build
curl --fail http://localhost:8080/readyz

Open Golf on localhost:8080 and Forgejo on localhost:3001. Readiness may return 503 while dependencies start. Use localhost consistently for the configured origin.

02 / ACCOUNT

Enrollment is deliberate.

Public registration is disabled.

Create a native identity

Use Forgejo’s supported administrator command, then create a scoped token in that user’s applications settings. Give each person their own identity.

Enroll a Golf account

Supply the native identity/token and a separate Golf password through an ignored private JSON input to the operator command. The installation guide has exact commands.

Inspect a repository

Sign into Golf. Create or open an allowed repository and inspect source, issues and PRs. Workers and integrations require their own enrollment/configuration.

Keep the installation intact.

LOCAL TERMINAL
docker compose stop
docker compose start
# Retains named volumes:
docker compose down

Preserve .env, encryption keys, both databases and Forgejo volumes. Never add --volumes as a routine restart. A complete current Forgejo restore still needs its own qualification.

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