foster/forgejo-docs
0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-11-21 17:36:59 -05:00
Code Issues Activity

docs: admin: actions: add missing actions

Browse source 
Fixes: https://codeberg.org/forgejo/website/issues/302
This commit is contained in:
Loïc Dachary 2023-07-18 09:06:54 +02:00 committed by Caesar Schinas
parent 8cfc9d602e
commit 89b2cbea3a
No known key found for this signature in database
GPG key ID: AE9108461BEA5ACF
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
admin/actions.md
View file

@ -128,7 +128,7 @@ When Infrastructure as Code (Ansible, kubernetes, etc.) is used to
deploy and configure both Forgejo and the Forgejo runner, it may be deploy and configure both Forgejo and the Forgejo runner, it may be
more convenient for it to generate a secret and share it with both. more convenient for it to generate a secret and share it with both.
The `forgejo forgejo-cli register --secret <secret>` subcommand can be The `forgejo forgejo-cli actions register --secret <secret>` subcommand can be
used to register the runner with the Forgejo instance and the used to register the runner with the Forgejo instance and the
`forgejo-runner create-runner-file --secret <secret>` subcommand can `forgejo-runner create-runner-file --secret <secret>` subcommand can
be used to configure the Forgejo runner with the credentials that will be used to configure the Forgejo runner with the credentials that will
@ -138,7 +138,7 @@ as it comes online.
For instance, on the machine running Forgejo: For instance, on the machine running Forgejo:
```sh ```sh
$ forgejo forgejo-cli register --name runner-name --scope myorganization \ $ forgejo forgejo-cli actions register --name runner-name --scope myorganization \
--labels docker \ --labels docker \
--secret 7c31591e8b67225a116d4a4519ea8e507e08f71f --secret 7c31591e8b67225a116d4a4519ea8e507e08f71f
``` ```
@ -150,7 +150,7 @@ $ forgejo-runner create-runner-file --instance https://example.conf \
--secret 7c31591e8b67225a116d4a4519ea8e507e08f71f --secret 7c31591e8b67225a116d4a4519ea8e507e08f71f
``` ```
> **NOTE:** the labels known to the runner are defined in the `config.yml` and **MUST** match the labels provided to the `forgejo-cli register` command above. In this example, `labels: ['docker:docker://node:16-bullseye']` will tell the Forgejo runner that when a **job** specifies `runs-on: docker`, it will run in a container created from the `node:16-bullseye` image by default. > **NOTE:** the labels known to the runner are defined in the `config.yml` and **MUST** match the labels provided to the `forgejo-cli actions register` command above. In this example, `labels: ['docker:docker://node:16-bullseye']` will tell the Forgejo runner that when a **job** specifies `runs-on: docker`, it will run in a container created from the `node:16-bullseye` image by default.
## Configuration ## Configuration