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_.
* all future release and EOL dates on Wednesdays
* v7 with EOL 2025
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/936
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Robert Wolff <mahlzahn@posteo.de>
Co-committed-by: Robert Wolff <mahlzahn@posteo.de>
Defaulting to docker_host: "" will expose the underlying docker socket
to all containers which is a security risk. The default must be the
most secure setup.
Change internal ssh port for rootless image to 2222 as the rootless image has ssh running on port 2222.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/895
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: apoorv569 <apoorv569@noreply.codeberg.org>
Co-committed-by: apoorv569 <apoorv569@noreply.codeberg.org>
The configuration cheat sheet isn't the canonical documentation for the
CLI and this particular bit has no relation to `ENABLE_PPROF` setting
anymore.
Resolves forgejo/forgejo#5268
- it is related to installation instructions
- mention SQLite in the guide
- reduce the complexity of the guide (I think we don't need to cover all the details here, there are better guides available)
As of forgejo/forgejo#2869, console logging implements three adaptations
for running forgejo under systemd/journald:
- forgejo learned to emit printk-style log level prefixes that are
picked up by journald and saved as the severity level of this line
(e.g., `<3>some text\n` means that "some text" will be saved as an
error entry);
- forgejo learned a new pseudo-flag "journaldflags" which is supposed to
replace "stdflags" when running under journald to reduce log clutter
(specifically, it removes date/time from log entries since the
time information is automatically saved by journald and displayed by
journalctl, and replaces the textual log level by the above-described
machine-parsable log level prefix);
- finally, forgejo will try to automatically detect whether it is
running under journald by parsing `$JOURNAL_STREAM` environment
variable and use "journalflags" as default flags if that is the case).
Document those.
Signed-off-by: Ivan Shapovalov <intelfx@intelfx.name>
This changes terminal command blocks to always use the multiline formatting,
as the leading octothorpe looks very strange when displaying a command inline.
Two consecutive inline commands at the start was very difficult to read in the
generated html. See:
https://forgejo.org/docs/latest/admin/installation-binary/
`HTTP_PORT` has been highlighted as a code term. This also means we don't need
to worry about another underscore in the same line being added and interpreted
as syntax.
Simplifies and fixes sentence structure in a few places. I've seen arguments
for and against the use of "just" in technical writing, but I think here it's
better without?
Reworded some paragraphs so that the command comes at the end.
This PR
- adds more details regarding the nature of the secret used when registering runners offline using `forgejo-cli actions register`,
- explains how to change the secret for an existing runner ([Forgejo PR #4619](https://codeberg.org/forgejo/forgejo/pulls/4619)),
- explains how to keep the Forgejo-side command idempotent if the labels aren't known ([Forgejo PR #4610](https://codeberg.org/forgejo/forgejo/pulls/4610))
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/769
Reviewed-by: twenty-panda <twenty-panda@noreply.codeberg.org>
Co-authored-by: Emmanuel BENOÎT <tseeker@nocternity.net>
Co-committed-by: Emmanuel BENOÎT <tseeker@nocternity.net>
