Per "request" of @0ko in https://codeberg.org/forgejo/forgejo/pulls/3270#issuecomment-1774032
TODOs
- postponed: how to add codespell (written in Python) to CI -- separate workflow? add to some other step? to some other tool/specification?
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/536
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
Co-committed-by: Yaroslav Halchenko <debian@onerussian.com>
- LTS are listed in the table, no hint in the version number
- update the RC release names
- CLI updates
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/561
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>
They get /forgejo/forgejo/archive/100448a007707c049a769cb71cd170fcb5b64a25.bundle
despite https://code.forgejo.org/robots.txt having
Disallow: /*/*/archive/
Disallow: /*/*/archive/*.bundle
* 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
