h759bkyo4/Documentation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Provide additional clarification for custom domains with Codeberg Pages (#293)

Browse source 
This provides more detail when using ALIAS+TXT DNS records.

More context:  https://matrix.to/#/!wkyjxWeAOBpKMvHbno:matrix.org/$Z0mdXrDKTNptIBpENaeZKd9WuuMWhCrawgIWsNjJjXo?via=freeyourgadget.org&via=matrix.org&via=tchncs.de

Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/293
Co-authored-by: Isaac Beverly <imbev@noreply.codeberg.org>
Co-committed-by: Isaac Beverly <imbev@noreply.codeberg.org>
This commit is contained in:
Isaac Beverly 2023-03-03 22:17:35 +00:00 committed by Otto
parent 4c425e13a4
commit 08986833f7
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/codeberg-pages/index.md
View file

@ -42,7 +42,7 @@ For custom domains, two things are required:
- `reponame.username.codeberg.page` → https://username.codeberg.page/reponame/
- `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 (`[[branch.]repo.]user.codeberg.page`, just as shown above for CNAME records).
The following sub-sections include a few examples of the different alternatives, assuming the following: