-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Fix some incorrect links in docs #28191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -114,7 +114,7 @@ If you cannot see the settings page, please make sure that you have the right pe | |
|
||
The format of the registration token is a random string `D0gvfu2iHfUjNqCYVljVyRV14fISpJxxxxxxxxxx`. | ||
|
||
A registration token can also be obtained from the gitea [command-line interface](../../administration/command-line.en-us.md#actions-generate-runner-token): | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Seems unnecessary prefix. Just There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ↑ The log above is incorrect because of the bug in But maybe it is better to let them in a same format. |
||
A registration token can also be obtained from the gitea [command-line interface](../../administration/command-line.md#actions-generate-runner-token): | ||
|
||
``` | ||
gitea --config /etc/gitea/app.ini actions generate-runner-token | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -113,7 +113,7 @@ Runner级别决定了从哪里获取注册令牌。 | |
|
||
注册令牌的格式是一个随机字符串 `D0gvfu2iHfUjNqCYVljVyRV14fISpJxxxxxxxxxx`。 | ||
|
||
注册令牌也可以通过 Gitea 的 [命令行](../../administration/command-line.en-us.md#actions-generate-runner-token) 获得: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. . |
||
注册令牌也可以通过 Gitea 的 [命令行](../../administration/command-line.md#actions-generate-runner-token) 获得: | ||
|
||
### 注册Runner | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -198,7 +198,7 @@ administrative user. | |
field is set to `mail.com`, then Gitea will expect the `user email` field | ||
for an authenticated GIT instance to be `[email protected]`.[^2] | ||
|
||
**Note**: PAM support is added via [build-time flags](installation/install-from-source.md#build), | ||
**Note**: PAM support is added via [build-time flags](installation/from-source.md#build), | ||
and the official binaries provided do not have this enabled. PAM requires that | ||
the necessary libpam dynamic library be available and the necessary PAM | ||
development headers be accessible to the compiler. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -162,7 +162,7 @@ PAM提供了一种机制,通过对用户进行PAM认证来自动将其添加 | |
- PAM电子邮件域:用户认证时要附加的电子邮件后缀。例如,如果登录系统期望一个名为gituse的用户, | ||
并且将此字段设置为mail.com,那么Gitea在验证一个GIT实例的用户时将期望user emai字段为[email protected][^2]。 | ||
|
||
**Note**: PAM 支持通过[build-time flags](installation/install-from-source.md#build)添加, | ||
**Note**: PAM 支持通过[build-time flags](installation/from-source.md#build)添加, | ||
而官方提供的二进制文件通常不会默认启用此功能。PAM需要确保系统上有必要的libpam动态库,并且编译器可以访问必要的PAM开发头文件。 | ||
|
||
[^1]: 例如,在Debian "Bullseye"上使用标准Linux登录,可以使用`common-session-noninteractive`。这个值对于其他版本的Debian, | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.