Codeberg Pages

"records": { "CNAME": "codeberg.page" }

Codeberg's own docs write this target with a trailing dot (codeberg.page.), the zone-file convention for "fully qualified, don't append anything." Our schema validates CNAME as a plain hostname and rejects the trailing dot, so leave it off here; the DNS record that gets created is equivalent either way.

1. Fork the registry and edit domains/you.json to the record above.
2. Open a pull request. Once merged, the CNAME is synced to DNS automatically. The current Codeberg Pages server treats the CNAME itself as authorization, so there is no separate .domains file to add to the Pages repo (that was only needed by the retired Pages Server v2).

Visiting https://you.runs-on.dev should serve the Pages site once DNS has propagated and Codeberg has issued a certificate, usually within a few minutes.