This provides more detail when using ALIAS+TXT DNS records.
@ -43,3 +43,3 @@
- `branchname.reponame.username.codeberg.page` → https://username.codeberg.page/reponame/@branchname/
If you can't use a CNAME record to configure the target (e.g. for a zone root), you can use an A/AAAA/ALIAS record to `codeberg.page` with an additional TXT record for the target (just as shown above for CNAME records).
If you can't use a CNAME record to configure the target (e.g. for a zone root), you can use an A/AAAA/ALIAS record to `codeberg.page` with an additional TXT record for the target (to `[[branch.]repo.]user.codeberg.page` just as shown above for CNAME records).
I'd remove the "to", might be subjective. I think we need a comma between the target and "just as shown ...".
Correct. The TXT record doesn't really point "to" anything, it's just a record that allows storing arbitrary textual data in DNS.
As I mentioned in the Matrix room before, I also think the IPv4 and IPv6 addresses should be listed for A and AAAA records respectively. Maybe it would even be better to replace this paragraph with a table showing which records you need for your particular setup and what their exact value should be.
There should also probably be a notice somewhere that the A/AAAA records will break if Codeberg's IP address changes for some reason. I don't know how the network is setup or what the likelihood of that scenario is but I do think it's worth noting.
Is there a reason to prefer A/AAAA over ALIAS?
As I stated in the Matrix room,
ALIAS records do not work correctly on DNSSEC signed zones and many providers simply do not support them.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?