GitHub mirror goes public #27

Open
opened 2026-07-25 16:26:13 +00:00 by Cordy · 3 comments
Owner

Publish the public GitHub mirror of the repo (currently private on Forgejo). Fair-code license (LICENSE.md) in place, marketing vocabulary "source-available"/"fair-code" (never "open source").

Final public-launch step; gated on v0.4 being a comfortably-deployable competitor.

Publish the public GitHub mirror of the repo (currently private on Forgejo). Fair-code license (`LICENSE.md`) in place, marketing vocabulary "source-available"/"fair-code" (never "open source"). Final public-launch step; gated on v0.4 being a comfortably-deployable competitor.
Cordy added this to the v1.0 - Go live milestone 2026-07-25 16:26:13 +00:00
Author
Owner

Triage: tandem (launch action, you drive). Make the GitHub mirror public. Gates #202 (switch update-check tagsUrl to GitHub) and the shipped update-check default. Part of the v0.8 going-public batch with #26.

**Triage: tandem (launch action, you drive).** Make the GitHub mirror public. Gates #202 (switch update-check `tagsUrl` to GitHub) and the shipped update-check default. Part of the v0.8 going-public batch with #26.
Author
Owner

Flag for the mirror-go-public checklist (from Nikola, 2026-09-25): the Administration → Updates section checks upstream against the internal Forgejo today — the dogfood banner literally shows Get "http://192.168.10.245/api/v1/repos/Cordy/Cairn/tags". When the GitHub mirror goes public (and again if the product is renamed per #563), this needs:

  • the update-check tagsUrl switched to the public GitHub repo (that is #202 — it becomes a hard dependency of this issue, not just a nice-to-have);
  • the tags-API response shape re-checked: Forgejo and GitHub both serve /tags, but via different API roots and pagination/rate-limit behaviour (GitHub unauthenticated = 60 req/h per IP — fine for a daily check, but worth a note in the code);
  • any default/fallback URL baked into config or code updated, plus the docs handbook line that describes what the check contacts;
  • #563 rename: repo path in the URL, and any user-facing "Cairn" strings in the Updates card.

Related bug found on the same screen (separate issue, being root-caused now): a stale "Update check failed: … context canceled" banner shows even after a later successful check.

Flag for the mirror-go-public checklist (from Nikola, 2026-09-25): the **Administration → Updates** section checks upstream against the internal Forgejo today — the dogfood banner literally shows `Get "http://192.168.10.245/api/v1/repos/Cordy/Cairn/tags"`. When the GitHub mirror goes public (and again if the product is renamed per #563), this needs: - the update-check `tagsUrl` switched to the public GitHub repo (that is #202 — it becomes a hard dependency of this issue, not just a nice-to-have); - the tags-API **response shape** re-checked: Forgejo and GitHub both serve `/tags`, but via different API roots and pagination/rate-limit behaviour (GitHub unauthenticated = 60 req/h per IP — fine for a daily check, but worth a note in the code); - any default/fallback URL baked into config or code updated, plus the docs handbook line that describes what the check contacts; - #563 rename: repo path in the URL, and any user-facing "Cairn" strings in the Updates card. Related bug found on the same screen (separate issue, being root-caused now): a stale "Update check failed: … context canceled" banner shows even after a later successful check.
Author
Owner

To do at go-live: deploy/chart/values.yaml still sets the default image.repository to the internal registry (192.168.10.245/cordy/cairn). Point it at the public image, and check the chart README / handbook install commands at the same time. I found this during the v0.6.338 review (#890); per Nikola, it changes here rather than in a patch release.

To do at go-live: `deploy/chart/values.yaml` still sets the default `image.repository` to the internal registry (`192.168.10.245/cordy/cairn`). Point it at the public image, and check the chart README / handbook install commands at the same time. I found this during the v0.6.338 review (#890); per Nikola, it changes here rather than in a patch release.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#27
No description provided.