mirror of
https://github.com/go-gitea/gitea.git
synced 2024-11-29 04:30:07 +08:00
Runner tokens are multi use (#29153)
Fixes https://github.com/go-gitea/gitea/issues/28911. Co-authored-by: Giteabot <teabot@gitea.io>
This commit is contained in:
parent
4f34691683
commit
4635e6d2a6
|
@ -120,6 +120,8 @@ A registration token can also be obtained from the gitea [command-line interface
|
|||
gitea --config /etc/gitea/app.ini actions generate-runner-token
|
||||
```
|
||||
|
||||
Tokens are valid for registering multiple runners, until they are revoked and replaced by a new token using the token reset link in the web interface.
|
||||
|
||||
### Register the runner
|
||||
|
||||
The act runner can be registered by running the following command:
|
||||
|
|
|
@ -61,8 +61,8 @@ It is always a bad idea to use a loopback address such as `127.0.0.1` or `localh
|
|||
If you are unsure which address to use, the LAN address is usually the right choice.
|
||||
|
||||
`token` is used for authentication and identification, such as `P2U1U0oB4XaRCi8azcngmPCLbRpUGapalhmddh23`.
|
||||
It is one-time use only and cannot be used to register multiple runners.
|
||||
You can obtain different levels of 'tokens' from the following places to create the corresponding level of' runners':
|
||||
Each token can be used to create multiple runners, until it is replaced with a new token using the reset link.
|
||||
You can obtain different levels of 'tokens' from the following places to create the corresponding level of 'runners':
|
||||
|
||||
- Instance level: The admin settings page, like `<your_gitea.com>/admin/actions/runners`.
|
||||
- Organization level: The organization settings page, like `<your_gitea.com>/<org>/settings/actions/runners`.
|
||||
|
|
Loading…
Reference in New Issue
Block a user