The shown command uses HEAD, so it will push the currently checked out
branch. Other non-HEAD examples will be shown further below.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/1083
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <n0toose@noreply.codeberg.org>
Co-authored-by: Rainer Müller <raimue@codingfarm.de>
Co-committed-by: Rainer Müller <raimue@codingfarm.de>
* better to not wait before swaggerfile on v9 becomes outdated
* unclosed bracket
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/1074
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Remove the suggestion to use image.container because it won't work as
expected. It is also confusing because LXC templates are not
conceptually equivalent to OCI.
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:
