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>
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>
(cherry picked from commit 2bb951215c)
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>
Although it was originally designed to run daily, the action cutting
the branch is better done in a central location, under the supervision
of the release manager who can check that each step goes as planned.
https://code.forgejo.org/forgejo/release-manager
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.
https://code.forgejo.org/forgejo/release-scheduler will
use the release info derived from release-schedule.json:
* for each release that is not EOL and for which the cut date is in
the past, ensure that:
* a v* branch exists or create it from next
* a backport/label exists or create it
* for each backport/* labels, archive those that match a release that
is EOL
This mainly came about because I noticed an inconsistency in the
`docs/user/actions.md` section, where it said a snippet ensures the usage
of _Alpine 3.18_, but the snippet actually obviously said _3.19_.
While I was at it, I just updated all mentions of Alpine I could find to
the current _3.20_.
