coulomb/railiance-forge
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Standardize public Gitea HTTPS endpoint
Some checks failed
Forge Runner Smoke / compatibility-smoke (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-13 18:52:58 +02:00
parent 5861c61c8e
commit a1b55776fa
9 changed files with 152 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/gitea-package-registry.md
View File

@@ -8,14 +8,15 @@ Gitea package support is enabled by `helm/gitea-registry-values.yaml`. That
overlay is applied after the encrypted base values by `make gitea-deploy` and
enables both container packages and Python packages.
The public ingress intentionally exposes `/api/packages` and `/v2` only. The
package route is required for Python package upload and install traffic; the
general Gitea web UI and API remain outside this ingress manifest.
The public ingress exposes the Gitea web route at
`https://gitea.coulomb.social/`, the Python package route at `/api/packages`,
and the OCI registry route at `/v2`. The standard endpoint is HTTPS; if package
simple-index pages render `http://gitea.coulomb.social/...` artifact links,
reconcile the Gitea Helm release with `helm/gitea-registry-values.yaml` so
`ROOT_URL` is restored to the HTTPS host.
The live simple-index pages currently render package artifact links with
`http://gitea.coulomb.social/...`. `uv lock` and clean `pip install` checks work
against the public package route, but the next Gitea config reconciliation
should align `ROOT_URL` with the HTTPS package endpoint.
Status on 2026-06-13: the root web route returns `200`, live `ROOT_URL` is
`https://gitea.coulomb.social/`, and package artifact links render HTTPS URLs.
## Python Packages