The upcoming 3.1 release of the Forgeo runner will allow to specify
which template and release must be must be used for a LXC
container. It also defines the lxc:// scheme as distinct from the
host:// scheme.
The host:// scheme is documented to be used for running jobs directly
from the host, which was not possible with the Forgejo runner versions
prior to 3.1
(cherry picked from commit 9c0d4b25e5)
- Update images to the 'new' design and have better consistency with
sizes (using Firefox's screenshot node feature).
- Add section for blocking users as a user of where to find the list of
blocked users and how to unblock them.
(cherry picked from commit fcb6347c18)
- [Shiki](https://github.com/shikijs/shiki) doesn't support highlighting
Go templates, so instead use handlebars template highlighting for this
code snippet.
(cherry picked from commit c8d40af3e2)
adding collaborators with write access to the destination repository
is a way for the author of a pull request to gain elevated privileges
(cherry picked from commit 533f575dde)
It provides two concrete examples to illustrate how they are
useful. It also explains how the permissions and tokens are created
and installed.
(cherry picked from commit 8cb1dbf218)
- split the installation page into separate pages for Docker, binary install, and packages
- clarify the next step is the installation page via the web
- clarify the first user created has admin rights
- clarify how values in the config sheet are provided when using Docker installation
- explain database preparation can be skipped if using SQLite which is built-in
Fixes: https://codeberg.org/forgejo/docs/issues/117
(cherry picked from commit 64ba97d470)
Documentation proposal for remote data mounting, following up from https://codeberg.org/forgejo/forgejo/issues/1590
Co-authored-by: Daniel Bischof <daniel.bischof@protonmail.com>
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/193
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: dbischof90 <dbischof90@noreply.codeberg.org>
Co-committed-by: dbischof90 <dbischof90@noreply.codeberg.org>
(cherry picked from commit cabb9fca11)
* the postgresql.yml file was merged into test.yml
* add links to test.yml directly rather than the directory to save one click
(cherry picked from commit c4a2a40f6f)
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)
