* added new step to check the activity in history
* renamed `Weblate repository admin page` to `repository management`
* placed it where it belongs: right before the mentions of buttons from that page
* clarified actions for the case of title having [skip ci]
* updated pull request prefix: `[I18N]` -> **i18n:**
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/902
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
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>
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 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>
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.
Rename Developer to Contributor guide
- I believe this sounds more inclusive and likely improves the diversity of contributors.
Separate translation section
clarify external resources
Add links to UI/UX and user research repos
Separate issue tracker and discussions
- I imagine this is part of the confusion for people who report bugs to the discussion tracker.
Add welcome section
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/821
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: Otto Richter <git@otto.splvs.net>
Co-committed-by: Otto Richter <git@otto.splvs.net>
