Greeting / "get up to speed" onboarding page with pasteable git-config snippet #20

New issue

Open

opened 2026-07-11 11:37:25 +02:00 by qwc · 0 comments

qwc commented

2026-07-11 11:37:25 +02:00

Owner

After logging into the web UI, every user should land on a greeting / "get up to speed" page built around a ready-to-paste git config snippet that routes their fetches through the proxy under their identity. This is the concrete destination the anonymous-fetch nudge points people to (see #19), but it's valuable on its own — it's how a new user gets configured correctly in one stop.

Requirements (to refine later)

Short explanation before the snippet. A sentence or two on what this does and why — routing your fetches through the proxy under your identity, so scans / quarantine / notify attribute to you — not just a naked code block.

Pasteable, personalized snippet. The user's minted token baked into the URL, e.g.:

git config --global url."https://<token>@proxy.example/repos/github.com/".insteadOf "https://github.com/"

The list can get LONG. There are many FOSS hosting origins in the wild (github.com, gitlab.com, codeberg.org, git.kernel.org, sourceforge, gnome/freedesktop GitLabs, bitbucket, savannah, …), each needing its own insteadOf line. So:
- Don't hand-wave a single line — generate the full block for the origins the proxy is configured to serve (drive it from the proxy's known/allowed upstream list, not a hardcoded snippet).
- Copy-to-clipboard button(s), and probably a download (.gitconfig fragment / shell script) since it may be dozens of lines.
- Possibly group "common" vs "all", or let the user tick which origins they need.
Stay in sync with config. The snippet is a view of TULLI_UPSTREAM_BASE / whatever upstream-origin allowlist the proxy grows, so it never drifts.
One stop for both transports. Natural home for the account's SSH-key upload and token management (already exist), so "how to get up to speed" covers both the HTTP-token and SSH paths.

Relationship to #19

#19 (discourage/disallow anonymous HTTP fetching) depends on this page existing — the nudge/enforce messaging tells users to "log in and configure git properly", and this is where they land. This issue can be built independently and first.

Labels: web, identity, Kind/Enhancement. Design/refine-later placeholder — no implementation yet.

After logging into the web UI, every user should land on a **greeting / "get up to speed" page** built around a **ready-to-paste git config snippet** that routes their fetches through the proxy under their identity. This is the concrete destination the anonymous-fetch nudge points people to (see #19), but it's valuable on its own — it's how a new user gets configured correctly in one stop. ## Requirements (to refine later) - **Short explanation before the snippet.** A sentence or two on *what* this does and *why* — routing your fetches through the proxy under your identity, so scans / quarantine / notify attribute to you — not just a naked code block. - **Pasteable, personalized snippet.** The user's minted token baked into the URL, e.g.: ```sh git config --global url."https://<token>@proxy.example/repos/github.com/".insteadOf "https://github.com/" ``` - **The list can get LONG.** There are many FOSS hosting origins in the wild (github.com, gitlab.com, codeberg.org, git.kernel.org, sourceforge, gnome/freedesktop GitLabs, bitbucket, savannah, …), each needing its own `insteadOf` line. So: - Don't hand-wave a single line — generate the **full block** for the origins the proxy is configured to serve (drive it from the proxy's known/allowed upstream list, not a hardcoded snippet). - **Copy-to-clipboard** button(s), and probably a **download** (`.gitconfig` fragment / shell script) since it may be dozens of lines. - Possibly group "common" vs "all", or let the user tick which origins they need. - **Stay in sync with config.** The snippet is a *view* of `TULLI_UPSTREAM_BASE` / whatever upstream-origin allowlist the proxy grows, so it never drifts. - **One stop for both transports.** Natural home for the account's SSH-key upload and token management (already exist), so "how to get up to speed" covers both the HTTP-token and SSH paths. ## Relationship to #19 #19 (discourage/disallow anonymous HTTP fetching) *depends on* this page existing — the nudge/enforce messaging tells users to "log in and configure git properly", and this is where they land. This issue can be built independently and first. Labels: `web`, `identity`, `Kind/Enhancement`. Design/refine-later placeholder — no implementation yet.

qwc added the

identity

Kind/Enhancement

web

labels

2026-07-11 11:37:34 +02:00

qwc referenced this issue

2026-07-11 11:37:41 +02:00

Option to discourage/disallow anonymous HTTP(S) fetching (first-fetch nudge → block, login for token URL) #19