Following thoughts lead to this pull-request:
1. now there is a place to collect information around federation.
2. mermaid handling inside of forgejo is more natural.
3. federation is not mirrored to code.forgejo, so I link to codeberg.
Close #1009.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/1055
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: Michael Jerger <michael.jerger@meissa-gmbh.de>
Co-committed-by: Michael Jerger <michael.jerger@meissa-gmbh.de>
They can be followed in sequential order which is more convenient and
requires less brain cells.
- isolate everything in containers to avoid undesirable interferences
with the local GPG agent
- --export-secret-keys must be --export-secret-subkeys otherwise
it also exports the master key
Adds support for the Apt-Rpm registry of the Alt Lunux distribution.
Alt Linux uses RPM packages to store and distribute software to its users. But the logic of the Alt Linux package registry is different from the Red Hat package registry.
I have added support for the Alt Linux package registry.
Related to : https://codeberg.org/forgejo/docs/pulls/978
Co-authored-by: gamzinav <gamzinav@basealt.ru>
Co-authored-by: Aleksandr Gamzin <gamzin@altlinux.org>
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/978
Reviewed-by: 0ko <0ko@noreply.codeberg.org>
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: Alex619829 <alex619829@noreply.codeberg.org>
Co-committed-by: Alex619829 <alex619829@noreply.codeberg.org>
Changed the Docker Docs to Forgejo 10
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/1038
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: Robin Kloppe <git@mainboarder.de>
Co-committed-by: Robin Kloppe <git@mainboarder.de>
Add documentation for how you can and do diagnostics/profiling in
Forgejo, it covers the methods that Forgejo offer for this,
nuances of the methods and potential footguns. I don't expect the
average forgejo adminstrator to be able to profile their Forgejo
instance (hence the warning in the first paragraph about contacting the
Forgejo developers) but for those brave enough this documentation should
be a solid foundation to get started.
This is complementatory the Forgejo PR about improving the diagnostics:
Preview: https://forgejo.codeberg.page/@docs_pull_998/docs/next/admin/runner-installation/#nixos
Fixes #903.
As described in that issue, the Nix package has been renamed upstream, as well as that the mentioned service module does not exist in reality.
I reworked that section to bring everything up-to-date. The mentioned labels pre-population does not apply to Forgejo, at least. I have also added a small example as reference.
Further, I included a small change to `scripts/preview.sh`, to detect the actual URL open command - on Linux, `xdg-open` is normally the canonical one.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/998
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Christoph Heiss <christoph@c8h4.io>
Co-committed-by: Christoph Heiss <christoph@c8h4.io>
The current description is pretty unclear on what the option actually
does (and the name isn't helpful either). Completely reword it, as well
as mentioning the default value too.
Signed-off-by: Christoph Heiss <christoph@c8h4.io>
In shell, prefixing a command with `sudo' only applies to the following command. Just as with newlines, semicolons and pipes, the AND (`&&') and OR (`||') operators separate commands.
Remove the recommendations to use issues to manage releases, with the
details about how to push tags manually. This is driven by tasks in
the release manager.
