Move git host to git.slipstreamviewer.org; host slipstreamviewer.org (.com redirect) #127

New issue

Closed

opened 2026-09-27 20:46:11 +00:00 by backspace119 · 1 comment

backspace119 commented

2026-09-27 20:46:11 +00:00

Owner

Move the Forgejo instance from git.goawayfbiman.com to git.slipstreamviewer.org, and put the new website on slipstreamviewer.org, with slipstreamviewer.com redirecting to it.

1. DNS / Cloudflare (both domains on Cloudflare)

git.slipstreamviewer.org → same origin as git.goawayfbiman.com (starswirl 192.168.96.20, via whatever tunnel/proxy git.goawayfbiman.com uses today), proxied.
slipstreamviewer.org + www → website origin, proxied; www 301 → apex.
slipstreamviewer.com + www.slipstreamviewer.com → Cloudflare redirect rule, 301 to https://slipstreamviewer.org${path}. No origin needed.
Keep git.goawayfbiman.com as a 301 to https://git.slipstreamviewer.org${path} indefinitely: every build shipped so far has goawayfbiman links baked in (Report Bug, release notes, downloads).
Note: the 100 MB Cloudflare upload cap still applies. CI already uploads over the LAN, so this is unchanged.

2. Forgejo (starswirl, `app.ini`) — server change, needs approval at the time

[server] DOMAIN = git.slipstreamviewer.org, ROOT_URL = https://git.slipstreamviewer.org/, SSH_DOMAIN = git.slipstreamviewer.org.
Origin TLS for the new hostname: a Cloudflare origin cert or LE, matching the current setup.
Restart Forgejo. Existing web sessions are invalidated, so users log in again. API tokens, SSH keys and repos are unaffected.
Registration / email settings: once the mail server exists, send from @slipstreamviewer.org.
Check the webhook and runner configs: the runner registers against the LAN URL, and CI uses the LAN API/git (RELEASE_API, REPO_GIT), so there should be no change.
Remaining SSH remote users on the old hostname keep working via the LAN IP. Public SSH via git.slipstreamviewer.org depends on how SSH is exposed today.

3. Website hosting

The site repo is ready (landing + about + MkDocs wiki; make build → public/).
Options, from least to most separated:
- nginx on starswirl;
- a small website LXC;
- Cloudflare Pages.
- Recommendation: nginx on starswirl (or the future build LXC, #103) serving public/, deployed by a Forgejo Actions workflow on push to the site repo's main.
Create the slipstream-website repo on Forgejo and push it.

4. Code / content updates (after DNS + Forgejo are live)

The viewer points at git.goawayfbiman.com/backspace119/Slipstream in:
- settings.xml (ReportBugURL);
- strings.xml / notifications.xml (issue tracker, release notes base URL, download links), en + ja;
- llerror.cpp (reinstall message);
- llappviewer.cpp (Discord rich-presence URL);
- installer_template.iss;
- README.md.
Point them at https://git.slipstreamviewer.org/... (or https://slipstreamviewer.org/... for downloads / docs), and give "download" links a stable https://slipstreamviewer.org/download that redirects to the latest release.
.forgejo/workflows/release.yml: RELEASE_API / REPO_GIT stay on the LAN; the public links in drafted notes follow ROOT_URL automatically.
Memory/docs: update the Forgejo references.

5. Order

Cloudflare DNS + origin cert for git.slipstreamviewer.org.
Forgejo ROOT_URL switch, and verify the web UI, clone and release downloads.
Add the 301 from goawayfbiman.
Website hosting + deploy workflow.
Update in-viewer URLs and ship them in the next release.

Move the Forgejo instance from **git.goawayfbiman.com** to **git.slipstreamviewer.org**, and put the new website on **slipstreamviewer.org**, with **slipstreamviewer.com** redirecting to it. ## 1. DNS / Cloudflare (both domains on Cloudflare) - `git.slipstreamviewer.org` → same origin as git.goawayfbiman.com (starswirl 192.168.96.20, via whatever tunnel/proxy git.goawayfbiman.com uses today), proxied. - `slipstreamviewer.org` + `www` → website origin, proxied; `www` 301 → apex. - `slipstreamviewer.com` + `www.slipstreamviewer.com` → Cloudflare redirect rule, 301 to `https://slipstreamviewer.org${path}`. No origin needed. - Keep **git.goawayfbiman.com** as a 301 to `https://git.slipstreamviewer.org${path}` **indefinitely**: every build shipped so far has goawayfbiman links baked in (Report Bug, release notes, downloads). - Note: the 100 MB Cloudflare upload cap still applies. CI already uploads over the LAN, so this is unchanged. ## 2. Forgejo (starswirl, `app.ini`) — server change, needs approval at the time - `[server] DOMAIN = git.slipstreamviewer.org`, `ROOT_URL = https://git.slipstreamviewer.org/`, `SSH_DOMAIN = git.slipstreamviewer.org`. - Origin TLS for the new hostname: a Cloudflare origin cert or LE, matching the current setup. - Restart Forgejo. Existing web sessions are invalidated, so users log in again. API tokens, SSH keys and repos are unaffected. - Registration / email settings: once the mail server exists, send from `@slipstreamviewer.org`. - Check the webhook and runner configs: the runner registers against the LAN URL, and CI uses the LAN API/git (`RELEASE_API`, `REPO_GIT`), so there should be no change. - Remaining SSH remote users on the old hostname keep working via the LAN IP. Public SSH via `git.slipstreamviewer.org` depends on how SSH is exposed today. ## 3. Website hosting - The site repo is ready (landing + about + MkDocs wiki; `make build` → `public/`). - Options, from least to most separated: - nginx on starswirl; - a small website LXC; - Cloudflare Pages. - Recommendation: nginx on starswirl (or the future build LXC, #103) serving `public/`, deployed by a Forgejo Actions workflow on push to the site repo's `main`. - Create the `slipstream-website` repo on Forgejo and push it. ## 4. Code / content updates (after DNS + Forgejo are live) - The viewer points at `git.goawayfbiman.com/backspace119/Slipstream` in: - `settings.xml` (`ReportBugURL`); - `strings.xml` / `notifications.xml` (issue tracker, release notes base URL, download links), en + ja; - `llerror.cpp` (reinstall message); - `llappviewer.cpp` (Discord rich-presence URL); - `installer_template.iss`; - `README.md`. - Point them at `https://git.slipstreamviewer.org/...` (or `https://slipstreamviewer.org/...` for downloads / docs), and give "download" links a stable `https://slipstreamviewer.org/download` that redirects to the latest release. - `.forgejo/workflows/release.yml`: `RELEASE_API` / `REPO_GIT` stay on the LAN; the public links in drafted notes follow `ROOT_URL` automatically. - Memory/docs: update the Forgejo references. ## 5. Order 1. Cloudflare DNS + origin cert for `git.slipstreamviewer.org`. 2. Forgejo `ROOT_URL` switch, and verify the web UI, clone and release downloads. 3. Add the 301 from goawayfbiman. 4. Website hosting + deploy workflow. 5. Update in-viewer URLs and ship them in the next release.

backspace119 referenced this issue from a commit

2026-09-27 22:45:49 +00:00

Point viewer links at git.slipstreamviewer.org

backspace119 commented

2026-09-28 05:27:13 +00:00

Author

Owner

Shipped: the viewer links point at git.slipstreamviewer.org (750287a2e3), released in v0.12.0-beta.1 / beta.2.

Shipped: the viewer links point at git.slipstreamviewer.org (750287a2e3), released in v0.12.0-beta.1 / beta.2.

backspace119 closed this issue

2026-09-28 05:27:13 +00:00