Fixes#646
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/647
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: Jan Koll <jan.niklas.koll@gmail.com>
Co-committed-by: Jan Koll <jan.niklas.koll@gmail.com>
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>
Given the plan to enable the storage quotas at some point in the future, instructions for how to reduce the size of git repos will become more relevant (and indeed, this has been a recurring question that came up on Codeberg, Matrix etc since announcing the quotas).
Building on @aral's draft in #418 I've gone ahead and took a stab at adding such a docs page, which hopefully helps outline the approach with enough warnings 😆Closes#418
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/639
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>
This adds a small section to the markdown link section of the docs to also outline the `[[ link ]]` syntax that is supported in markdown texts that are rendered to html.
Closes#524.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/638
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: Bastian Greshake Tzovaras <bgreshake@googlemail.com>
Co-committed-by: Bastian Greshake Tzovaras <bgreshake@googlemail.com>
This is targeted to close both #545 and #595 by
* explicitly mentioning the Woodpecker target
* link to the actions meta repo that provides some overview on Actions & Woodpecker
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/635
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: Bastian Greshake Tzovaras <bgreshake@googlemail.com>
Co-committed-by: Bastian Greshake Tzovaras <bgreshake@googlemail.com>
- Added Ente Auth to list of 2FA apps due to its open source/E2EE/cross platform nature
- Added links to the relevant user settings for SSH keys
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/634
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: Pigeon-AFA <antifantwerp@proton.me>
Co-committed-by: Pigeon-AFA <antifantwerp@proton.me>
Adds a method for using `wl-clipboard` to copy the SSH key on Wayland compositors.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/631
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: aec <aec@noreply.codeberg.org>
Co-committed-by: aec <aec@noreply.codeberg.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>
For some reason neither the docker image nor pnpm serve work on my machine.
TODO:
- [ ] test examples
- [ ] finish polishing
- [ ] add the rest of the references
- [ ] add helm details
- [ ] add autoscaler details
Co-authored-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: pat-s <pat-s@noreply.codeberg.org>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/554
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: Christopher A. Grant <chris@aptenodytes.ca>
Co-committed-by: Christopher A. Grant <chris@aptenodytes.ca>
# 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 noticed that Codeberg was referring to v1.19 of Forgejo.
Given that Forgejo's documentation is quite stable I feel like it
makes more sense to refer to the latest version of the docs instead.
Signed-off-by: Ryuno-Ki <andre.jaenisch@posteo.de>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/622
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: Ryuno-Ki <andre.jaenisch@posteo.de>
Co-committed-by: Ryuno-Ki <andre.jaenisch@posteo.de>
Weblate can also be configured to push directly to the Codeberg repo
but that requires adding the `translate` user as a collaborator in the
respective repo.
Also use this opportunity to improve grammar/formulations.
Closes: #324
Co-authored-by: Gusted <postmaster@gusted.xyz>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/481
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: Alex <alex@puer-robustus.eu>
Co-committed-by: Alex <alex@puer-robustus.eu>
Clarified where the user should Forgejo Actions.
Thanks to @gusted:matrix.org
Co-authored-by: plfarinha <plfarinha@noreply.codeberg.org>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/590
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: yaroze <yaroze@noreply.codeberg.org>
Co-committed-by: yaroze <yaroze@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>
