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_.
(cherry picked from commit 681f3a8369)
The config section can be easily missed when someone intends to only use the token as an env var. But that section contains the crucial bit of information about formatting the token.
This splits the credentials info from configuration description and makes the format explicit. While at it, the necessary permission is highlighted.
This should fix Codeberg/Community#1701
Co-authored-by: Earl Warren <earl-warren@noreply.codeberg.org>
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/939
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: dcz_pf <cobepfac.dcz@porcupinefactory.org>
Co-committed-by: dcz_pf <cobepfac.dcz@porcupinefactory.org>
(cherry picked from commit 2bb8cbc603)
* 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>
(cherry picked from commit 5fbb96de9f)
Document the "scopes" field that is now required when generating API tokens. Refer to the documentation of scope names.
Signed-off-by: julianfoad <julian@foad.me.uk>
(cherry picked from commit 953989cd7e)
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.
(cherry picked from commit 1f260c1254)
Hi, I just encountered this small issue when trying to build forgejo.
I could update this in other places as well if needed, but for now I assumed the `next` branch would be a good start.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/897
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: marcus doescher <deh.marcus@posteo.net>
Co-committed-by: marcus doescher <deh.marcus@posteo.net>
(cherry picked from commit eb58d4d121)
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>
(cherry picked from commit bd7373c0d8)
v9.0 is compatible with Gitea v1.22 because Gitea v1.23 branch is not
cut yet and it won't be released in the next few days.
(cherry picked from commit 6eb5c6fbf3)
The https://code.forgejo.org/infrastructure organization was created
recently to host infrastructure resources. The documentation should go there
instead of the Forgejo documentation.
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 simplifies the setup instructions and the skill requirements for
devops to use nginx to forward all ports instead of a mix of nftables
& nginx.
Also supports IPv6 and not just IPv4.
This has been adapted from
https://codeberg.org/Codeberg/Documentation/src/branch/main/content/git/using-tags.md,
and updated to document the changes from
https://codeberg.org/forgejo/forgejo/pulls/1445.
Co-authored-by: n <n@noreply.codeberg.org>
Co-authored-by: Gerhard Beck <gerhard.beck@elkb.de>
Co-authored-by: Jeremy <jeremytbaxter@protonmail.com>
Co-authored-by: Jeremy <jtbx@duck.com>
Co-authored-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: William Davis <unbeatable-101@noreply.codeberg.org>
Co-authored-by: crapStone <crapstone01@gmail.com>
Co-authored-by: f0sh <f0sh@mailbox.org>
Co-authored-by: fnetx <git@fralix.ovh>
Co-authored-by: mutluyuz <mutluyuz@noreply.codeberg.org>
Co-authored-by: n0toose <git@n0toose.net>
- 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>
