dallasgroot/Documentation
1
0
Fork 0
mirror of https://codeberg.org/Codeberg/Documentation.git synced 2026-06-16 05:13:54 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

main (#644)

Browse source 
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>
This commit is contained in:
freyalin 2025-07-18 16:39:24 +02:00 committed by Bastian Greshake Tzovaras
parent 78e5235f20
commit aaede8c9bb
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/codeberg-pages/pushing-output.md
View file

@ -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.