Document the `Allow anyone to edit the Wiki` option in `Settings`, and
the consequences of activating it.
Signed-off-by: Gergely Nagy <me@gergo.csillger.hu>
* switch to using lxc-helpers alone instead of enough
the learning curve of
[enough](https://enough-community.readthedocs.io) is an unecessary
burden in this context. Manual installation with lxc-helpers and
documentation is enough when there only is a need for a handful
of manual intervention per year
* update the Forgejo runner installation instructions
* tested the docker + self-hosted label to work with a test workflow
* do not maintain and setup a self-signed certificate because it creates a
complication that is unecessary when behind a VPN
In `admin/database-preparation` suggest `utf8mb4_bin` as the collate
function, rather than `utf8mb4_unicode_ci`. The former is accent- and
case sensitive, while the latter isn't, and Forgejo assumes that columns
are case sensitive.
Also add a short paragraph explaining why `utf8mb4_bin` is
suggested (case sensitivity), and what problems may arise and why if
case insensitive collation is used.
This partially addresses forgejo/forgejo#2039.
Signed-off-by: Gergely Nagy <me@gergo.csillger.hu>
Add a description of the steps necessary to migrate a Gitea installation to Forgejo on Arch Linux using the native packages.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/298
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Paul Sargent <psarge@gmail.com>
Co-committed-by: Paul Sargent <psarge@gmail.com>
No information in the root filesystem is really worth saving as it
can be recreated from this documentation or even from scratch manually
if needs be. But it is cheap to keep that backup and it is worth the
effort if it can save a few hours of work when an accident happen.
The more sophisticated way to do it would be to setup DRBD with the
root file system. But this is not straightforward and to ensure it
won't get the admin in trouble when an accident happen is tricky. It
is the one time when every bit of complication can quickly become a
blocker or an unecessary burden.
next.forgejo.org has been lagging for a few weeks in upgrades. While
crystal and dachary are busy, I setup and documented an LXC container
on the machine to which we all have access. It can be switched back to
where it was by updating the DNS entry.
