* Release number is v7.0.0+1.22.0 and following semantic versioning
* Remove the workflow page which is no longer needed as:
* it is implicitly understood pull requests go to the default branch
* testing requirements are documented in the testing.md page
* Explain how to cut a release and set the tag in forgejo-integration
for proper numbering of the test releases that come out of the
development branch
Refs: https://codeberg.org/forgejo/forgejo/pulls/2448
Preview: https://forgejo.codeberg.page/@docs_pull_427/docs/next/admin/customization/
---
The previous version of this document insinuated that you need to be
familiar with Forgejo's source code and compile Forgejo from source
for custom branding changes. As of the most recent Forgejo version,
this is not necessarily true, as custom files can be served from
the CustomPath.
Administrators that were not developers therefore dismissed the
other guide and its contents without reading this, and I was one
of them. I thought it would make sense for this file to provide
information on where to put a custom logo. This change does not
fix it (this will be done later), but it will reduce the confusion
for now.
This warning confused me personally and other Forgejo users, as I
had one person tell me IRL that they thought that it was not possible
to serve a custom logo.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/427
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-committed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
instead of keeping a backup within the container itself, trigger the
backup external to the container to make sure it reflects the state of
the container after Forgejo is shutdown in case it needs to be
retrieved.
* hint to use `make help` for target information
* require Go v1.21
* remove some redundant / obsolete strings
* `TAGS='sqlite sqlite_unlock_notify' make watch` because it is not
much use without sqlite
* 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
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.
