migrate forgejo.org #23

New issue

Open

opened 2025-12-08 12:51:38 +00:00 by Ghostinvisible-forgejo-org · 5 comments

Ghostinvisible-forgejo-org commented

2025-12-08 12:51:38 +00:00

See https://invisible.forgejo.org/infrastructure/k8s-cluster/src/branch/main/flux/apps/static-site

Refs: https://codeberg.org/forgejo/governance/issues/36

See https://invisible.forgejo.org/infrastructure/k8s-cluster/src/branch/main/flux/apps/static-site Refs: https://codeberg.org/forgejo/governance/issues/36

🚀 1

Ghostinvisible-forgejo-org commented

2025-12-08 12:51:39 +00:00

Author

this would allow us to use forgejo.org/v2 as transparent docker proxy, so docker images could be referenced as forgejo.org/oci/ci or forgejo.org/forgejo/forgejo 🙃

this would allow us to use `forgejo.org/v2` as transparent docker proxy, so docker images could be referenced as `forgejo.org/oci/ci` or `forgejo.org/forgejo/forgejo` 🙃

viceice commented

2025-12-08 12:51:39 +00:00

so the steps are:

create a repo at code.forgejo.org/forgejo/website
create a deploy key (ssh)
add it to codeberg.org/forgejo/website as secret
update push workflow to push to forgejo-code repo
add publish workflow to code.forgejo.org/forgejo/website

so the steps are: - create a repo at code.forgejo.org/forgejo/website - create a deploy key (ssh) - add it to codeberg.org/forgejo/website as secret - update push workflow to push to forgejo-code repo - add publish workflow to code.forgejo.org/forgejo/website

👍 1

earl-warren commented

2025-12-08 12:51:39 +00:00

See https://invisible.forgejo.org/infrastructure/k8s-cluster/src/branch/main/docs/k8s-static.md for details

viceice commented

2025-12-08 12:51:40 +00:00

a solution would be to use dns challenge, but that needs dns write access. this works fine on my other clusters.

benefits:

wildcard certificates (eg *.next.forgejo.org) (less renewals)
get certificate without waiting for ip adress change

dns with ovh works fine with cert-manager-webhook-ovh Helm chart cert-manager-webhook-ovh

everything is prepared so far. we need to extend the static site to accept more hostnames. sadly there is a period while the dns propagation piles up and we maybe don't get the proper certificate in time. a solution would be to use dns challenge, but that needs dns write access. this works fine on my other clusters. benefits: - wildcard certificates (eg `*.next.forgejo.org`) (less renewals) - get certificate without waiting for ip adress change dns with ovh works fine with [`cert-manager-webhook-ovh Helm chart cert-manager-webhook-ovh `](https://artifacthub.io/packages/helm/cert-manager-webhook-ovh/cert-manager-webhook-ovh)

viceice commented

2025-12-08 12:51:40 +00:00

nearly done, we just need the www.forgejo.org redirect, which is currently done by spoink.ip.crystalc.net from @crystal

nearly done, we just need the `www.forgejo.org` redirect, which is currently done by `spoink.ip.crystalc.net` from @crystal