See 9b698362a3
Also remove the token line from the .runner file. It is confusing and
difficult to explain because it is different from the registration
token. It really is a shared secret between the runner and the Forgejo
instance that has a purpose which is entirely different.
(cherry picked from commit 142d8a03d1)
Downgrade is never supported, there is no need to include details in
the documentation about the database versions.
(cherry picked from commit a0b72f9d49)
Caution: it needs to be squashed before merge to be backported. It is kept as two commits to preserve the original version.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/146
Reviewed-by: Loïc Dachary <dachary@noreply.codeberg.org>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>
(cherry picked from commit 43a07a1cba)
Also use YAML pseudo path as chapter headings because it makes it easier to find from the TOC
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/102
Reviewed-by: Caesar Schinas <caesar@caesarschinas.com>
Reviewed-by: Forgejo Release Team <release-team@noreply.codeberg.org>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>
The original documentation was written with a focus on local storage
and missed a few important aspects of how storage types can be mixed
together in some subsystems.
* unify the susbsystem paths to be "directory" instead of using "base
path". It is not technically a directory in S3 but looks like one
and the approximation is unlikely to cause confusion.
* use S3 instead of minio where possible to emphasize the storage type
is not MinIO specific and add a section for the compatibility with
garage
* change the document structure to have two separate parts:
* [storage] the global sections
* [xxxx] the subsystem specific section
and within each of them local and S3 are documented separately
because they share nothing
* [storage] is documented to be a fallback if [xxxx] does not exist
for a given subsystem. There is no notion of inheritance because
it behaves in ways that are not tested and for which consistency is
not guaranteed
* backward compatibility with Gitea is documented to be the reason why
there are no safeguards against undocumented features
