Release docs still point at the retired Gitea (git.riverofglorymn.org, now 502); no README #5

New Issue

2026-10-14T04:31:34Z

ekklesia-bot commented

2026-10-14 04:31:34 +00:00

Summary

The repository moved to Zayin/Classroom_Desktop on git.zayin.net, but its release documentation still names the old Gitea, which now answers HTTP 502. Someone following docs/releasing.md months from now, its stated audience, would point tools and runners at a dead instance. There's also no README at the repository root, so the Gitea front page and a new contributor have no entry point to the extensive docs/.

Where

File	Line	Says	Should say
`docs/releasing.md`	234–235	`export GITEA_URL=https://git.riverofglorymn.org` / `GITEA_REPO=River_of_Glory_Church/Ekklesia_Classroom`	`https://git.zayin.net` / `Zayin/Classroom_Desktop`
`docs/releasing.md`	392	`act_runner register --instance https://git.riverofglorymn.org …`	the Zayin instance
`tools/gitea-release`	36–37 (help text only; CI takes `GITHUB_SERVER_URL`/`GITHUB_REPOSITORY`)	the same old URL and repository	the Zayin values

https://updates.riverofglorymn.org is not stale: it's the live update server and answers correctly (stable 0.2.6.4, canary 0.2.6.6). Leave every updates.riverofglorymn.org reference alone. Likewise 10.40.0.2 is the church server (MQTT broker, update server's address from the runner), not the old Gitea.

Suggested change

Update the three places above, and re-read docs/releasing.md → Gitea administration still to do and Runners against the Zayin instance's real runners (see #4).
Add a short root README.md: what Ekklesia Classroom is, how a laptop gets it (channels and the update server), tools/check.sh / tools/build-release.sh, and a map of docs/ (releasing.md, testing.md, provisioning.md, backlog.md, …).

Found by Claude during a review of Classroom_Desktop's CI, 2026-10-14 (found-by-claude).

## Summary The repository moved to `Zayin/Classroom_Desktop` on `git.zayin.net`, but its release documentation still names the old Gitea, which now answers **HTTP 502**. Someone following `docs/releasing.md` months from now, its stated audience, would point tools and runners at a dead instance. There's also no `README` at the repository root, so the Gitea front page and a new contributor have no entry point to the extensive `docs/`. ## Where | File | Line | Says | Should say | |---|---|---|---| | `docs/releasing.md` | 234–235 | `export GITEA_URL=https://git.riverofglorymn.org` / `GITEA_REPO=River_of_Glory_Church/Ekklesia_Classroom` | `https://git.zayin.net` / `Zayin/Classroom_Desktop` | | `docs/releasing.md` | 392 | `act_runner register --instance https://git.riverofglorymn.org …` | the Zayin instance | | `tools/gitea-release` | 36–37 (help text only; CI takes `GITHUB_SERVER_URL`/`GITHUB_REPOSITORY`) | the same old URL and repository | the Zayin values | `https://updates.riverofglorymn.org` is **not** stale: it's the live update server and answers correctly (stable 0.2.6.4, canary 0.2.6.6). Leave every `updates.riverofglorymn.org` reference alone. Likewise `10.40.0.2` is the church server (MQTT broker, update server's address from the runner), not the old Gitea. ## Suggested change - Update the three places above, and re-read `docs/releasing.md` → *Gitea administration still to do* and *Runners* against the Zayin instance's real runners (see #4). - Add a short root `README.md`: what Ekklesia Classroom is, how a laptop gets it (channels and the update server), `tools/check.sh` / `tools/build-release.sh`, and a map of `docs/` (`releasing.md`, `testing.md`, `provisioning.md`, `backlog.md`, …). --- _Found by Claude during a review of Classroom_Desktop's CI, 2026-10-14 (`found-by-claude`)._

ekklesia-bot referenced this issue

2026-10-14 04:31:42 +00:00

Release pipeline is not set up on the Zayin Gitea: no release records, admin checklist still open #4

ekklesia-bot referenced this issue

2026-10-14 04:35:21 +00:00

State of Classroom_Desktop (review 2026-10-14) and a suggested order of work #6

ekklesia-bot added the found-by-claude label 2026-10-14 04:40:49 +00:00

Sign in to join this conversation.