This is an attempt to try fixing CI errors, as seen in 38dd33d Woodpecker run. Might not be complete, but the only thing missing is Apple Authenticator link fix, which is flaky.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/857
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Added a warning about the test delivery button being misleading for verifying pages webhook setup.
When pressed on a correctly configured webhook, it results in an error: `401 ref refs/heads/main not in allowlist [refs/heads/pages]`. This is both confusing and misleading; changing the branch filter also doesn't fix it.
I was helping a friend set up a pages site and we ran into this and were stuck until we guessed that the test itself doesn't work.
The docs don't explicitly say to use the test delivery button, but it is *right there* so we assumed we should use it. I think a note about not using it would help.
ty codeberg ur great
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/853
Reviewed-by: Catherine <whitequark@whitequark.org>
Missed a spot in #836 because DNSSEC was spelled weird. Also moved the
useful link to the DNSSEC verification tool to more relevant secions.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/837
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Closes#335.
This is my first attempt coding for eleventy/liquid so I'd be happy to get feedback on making the code cleaner or more idiomatic, or just more like the Codeberg style.
Co-authored-by: David Anselmi <danselmi@intecrowd.com>
Co-authored-by: Gusted <postmaster@gusted.xyz>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/780
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
- remove codeberg.page from .domains, it's redundant, the pages-server
does not validate the .domains file for codeberg.page domains
- add information for www-apex redirects to apex examples
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/557
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: crystal <crystal@noreply.codeberg.org>
Co-committed-by: crystal <crystal@noreply.codeberg.org>
I think this was a copy-paste error. But you cannot have both A and CNAME records on the same name. Only A/AAAA/TXT are the records needed here.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/671
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: kevinhikaruevans <kevinhikaruevans@noreply.codeberg.org>
Co-committed-by: kevinhikaruevans <kevinhikaruevans@noreply.codeberg.org>
Hi,
coming from https://codeberg.org/Codeberg/pages-server/issues/512, this adds a warning that repos with dots in the name can cause issues when trying to set up a custom domain.
I'm not sure if the wording here fits the existing docs, or if hints like this fit in the docs at all, but I wanted to open this as a suggestion nonetheless :)
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/670
Reviewed-by: Bastian Greshake Tzovaras <gedankenstuecke@noreply.codeberg.org>
Co-authored-by: Kilian Koeltzsch <me@kilian.io>
Co-committed-by: Kilian Koeltzsch <me@kilian.io>
Greetings,
I have been using Hugo and hosted Forgejo Actions to publish the static site to Codeberg Pages, and I noticed that there's no instructions on automatic deploy with custom domain. It's worth noticing that `.domains` file should be placed at the `static` directory for Hugo, and accordingly for other SSGs, instead of root of source repository, in order to preserve it to the output branch. I will also initiate a PR to Hugo documents regarding the sample Forgejo Action `hugo.yaml` setup.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/644
Reviewed-by: Bastian Greshake Tzovaras <gedankenstuecke@noreply.codeberg.org>
Co-authored-by: freyalin <xlin@mailbox.org>
Co-committed-by: freyalin <xlin@mailbox.org>
In #601, the suggestion was made to provide details on how to use a CI to get a website published to Codeberg Pages when using a static site generator.
We already provide a lot of details on that via the Woodpecker CI examples repo, so I've linked to that to help people find those details!
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/628
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: Bastian Greshake Tzovaras <bgreshake@googlemail.com>
Co-committed-by: Bastian Greshake Tzovaras <bgreshake@googlemail.com>
# Changelog
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
## Changed
- Refactor tables to respect `indent_size = 1`.
## Fixed
- Tables with `<tr>` and `<td>` tags in wrong ending order.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/627
Reviewed-by: Bastian Greshake Tzovaras <gedankenstuecke@noreply.codeberg.org>
Co-authored-by: Javier Pérez <walpo@noreply.codeberg.org>
Co-committed-by: Javier Pérez <walpo@noreply.codeberg.org>
I'm approaching the "transparency" proposal by @fnetX in Codeberg-e.V./Discussion#124
This should set the expectations of users using this feature to a more realistic setting (at least if they read the documentation). If this MR gets accepted, we can adapt the landing page afterward to include the same text.
cc @crapStone
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/585
Reviewed-by: Otto <otto@codeberg.org>
Reviewed-by: crapStone <codeberg@crapstone.dev>
Co-authored-by: Bene <bene64@posteo.de>
Co-committed-by: Bene <bene64@posteo.de>
Update Gitea link to Forgejo link.
Add GNU link to ignore.
Remove recommendation for Atom (no longer maintained) instead recommend VSCodium.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/484
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-committed-by: Gusted <postmaster@gusted.xyz>
fix#148
Adds a spell checker via `cspell` and fixes some spelling issues in the docs.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/439
Co-authored-by: pat-s <patrick.schratz@gmail.com>
Co-committed-by: pat-s <patrick.schratz@gmail.com>
Many users setting up Codeberg Pages that use the records have limited experience with DNS.
Therefore, adding this warning to make it clear what they may need to be entering into
their records will likely save them time and effort in troubleshooting why their page may
not be loading correctly.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/431
Co-authored-by: Sammy Hori <sammyhori@noreply.codeberg.org>
Co-committed-by: Sammy Hori <sammyhori@noreply.codeberg.org>
I believe the "pip" in front is extraneous. This is a small change.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/397
Co-authored-by: kouett <lou@ynh.kouett.net.eu.org>
Co-committed-by: kouett <lou@ynh.kouett.net.eu.org>
Main changes include switching language from ISP to domain registrar, and standardization around the phrase "Codeberg Pages".
Signed-off-by: Mark Pitblado <mark@pitblado.me>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/391
Reviewed-by: crapStone <codeberg@crapstone.dev>
Co-authored-by: Mark Pitblado <mark-pitblado@noreply.codeberg.org>
Co-committed-by: Mark Pitblado <mark-pitblado@noreply.codeberg.org>
- Formatting fixes, relevant text adjustments
- Some more complicated cases (e.g. attribution), as well as outdated
information that should be removed in a later commit were
deliberately left unchanged.
- Some minor mistakes (speling, trailing whitespaces, punctuation)
in the admonition boxes were also fixed.
