dallasgroot/Documentation
1
0
Fork 0
mirror of https://codeberg.org/Codeberg/Documentation.git synced 2026-08-15 14:53:29 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

pages: Use example.org in all git-pages examples

Browse source
This commit is contained in:
Artyom Bologov 2026-07-22 01:45:58 +04:00
parent eb35b4a18c
commit c889194235
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/codeberg-pages/troubleshooting.md
View file

@ -41,7 +41,7 @@ Say, we add this (broken) [redirect rule](/codeberg-pages/advanced-usage/#redire
/*/ /:splat.html 301 /*/ /:splat.html 301
``` ```
After committing it and opening a page like `https://website.tld/hello`, we are redirected to a 404 page. After committing it and opening a page like `https://example.org/hello`, we are redirected to a 404 page.
Something must be brokein in redirects. Something must be brokein in redirects.
However, we don’t know that for sure. However, we don’t know that for sure.
Need to check. Need to check.
@ -50,9 +50,9 @@ There are two ways to find out what’s broken in the website:
``` ```
# Plain web request # Plain web request
curl https://website.tld/.git-pages/manifest.json curl https://example.org/.git-pages/manifest.json
# Or a dedicated tool from git-pages # Or a dedicated tool from git-pages
git-pages-cli --debug-manifest https://website.tld git-pages-cli --debug-manifest https://example.org
``` ```
In either case, you get huge JSONs with meta-information about the website. In either case, you get huge JSONs with meta-information about the website.