From aaede8c9bbcac5fa076709a8c8ef3f5d703d4dd8 Mon Sep 17 00:00:00 2001 From: freyalin Date: Fri, 18 Jul 2025 16:39:24 +0200 Subject: [PATCH] main (#644) 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 Co-authored-by: freyalin Co-committed-by: freyalin --- content/codeberg-pages/pushing-output.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/codeberg-pages/pushing-output.md b/content/codeberg-pages/pushing-output.md index f4dcab1..233db64 100644 --- a/content/codeberg-pages/pushing-output.md +++ b/content/codeberg-pages/pushing-output.md @@ -101,3 +101,5 @@ For the Woodpecker CI, you can see the [existing example workflows in the `Codeb Currently, we do not have any examples for the Forgejo Actions yet, but individual SSG tools might have details in their own documentation: - [Hugo docs on using Forgejo Actions for Codeberg Pages](https://gohugo.io/host-and-deploy/host-on-codeberg-pages/#automated-deployment-using-forgejo-actions) + +Note that if you use Forgejo Actions to publish the website, you should make sure that `.domains` file will be preserved in the root directory of the **output** branch or repository.