Skip to content

git-proxy.md

Latest commit

 

History

History
37 lines (27 loc) · 1.45 KB

git-proxy.md

File metadata and controls

37 lines (27 loc) · 1.45 KB
Raw
title Git Proxy

Git Proxy

Git Proxy

Public HTTPS Git access for external tools (Databricks, CI/CD)

Nginx reverse proxy that forwards Git HTTPS requests to Forgejo. Provides public Git clone/push/pull access for external tools without exposing the Forgejo Web UI.

Setting Value
Default Port 3201 (-> internal 80)
Suggested Subdomain git
Public Access Yes (no Cloudflare Access)

How It Works

External tools ──HTTPS──> git.<domain> (PUBLIC)
                               │ (Cloudflare Tunnel)
                         Nginx (:3201)
                               │ (proxy_pass)
                         Forgejo (:3000) (PRIVATE)
  • External tools (Databricks) use https://git.<domain>/<user>/<repo>.git with Forgejo PAT
  • Internal services (Jupyter, etc.) use http://forgejo:3000 directly via Docker network
  • Forgejo Web UI at https://forgejo.<domain> remains private (Cloudflare Access OTP)

Usage with Databricks

  1. Create a Personal Access Token (PAT) in Forgejo
  2. In Databricks, add Git Credentials: select "GitHub" as the provider (Databricks does not list Forgejo, and the GitHub provider is used because both speak the same Git HTTPS + token protocol — a workaround, not a supported combination), then use your Forgejo username + PAT
  3. Clone repos via: https://git.<domain>/<user>/<repo>.git