diff --git a/docs/administration/cmd-embedded.md b/docs/administration/cmd-embedded.md index a7a4db72..1ee09626 100644 --- a/docs/administration/cmd-embedded.md +++ b/docs/administration/cmd-embedded.md @@ -19,7 +19,7 @@ menu: Gitea's executable contains all the resources required to run: templates, images, style-sheets and translations. Any of them can be overridden by placing a replacement in a matching path -inside the `custom` directory (see [Customizing Gitea](administration/customizing-gitea.md)). +inside the `custom` directory (see [Customizing Gitea](../administration/customizing-gitea.md)). To obtain a copy of the embedded resources ready for editing, the `embedded` command from the CLI can be used from the OS shell interface. @@ -85,7 +85,7 @@ The default is the current directory. The `--custom` flag tells Gitea to extract the files directly into the `custom` directory. For this to work, the command needs to know the location of the `app.ini` configuration file (`--config`) and, depending of the configuration, be ran from the directory where -Gitea normally starts. See [Customizing Gitea](administration/customizing-gitea.md) for details. +Gitea normally starts. See [Customizing Gitea](../administration/customizing-gitea.md) for details. The `--overwrite` flag allows any existing files in the destination directory to be overwritten. diff --git a/docs/administration/config-cheat-sheet.md b/docs/administration/config-cheat-sheet.md index 6be6f89d..cb316ece 100644 --- a/docs/administration/config-cheat-sheet.md +++ b/docs/administration/config-cheat-sheet.md @@ -764,7 +764,7 @@ and - `FORCE_TRUST_SERVER_CERT`: **false**: If set to `true`, completely ignores server certificate validation errors. This option is unsafe. Consider adding the certificate to the system trust store instead. - `USER`: **_empty_**: Username of mailing user (usually the sender's e-mail address). - `PASSWD`: **_empty_**: Password of mailing user. Use \`your password\` for quoting if you use special characters in the password. - - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](administration/email-setup.md) for more information. + - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](../administration/email-setup.md) for more information. - `ENABLE_HELO`: **true**: Enable HELO operation. - `HELO_HOSTNAME`: **(retrieved from system)**: HELO hostname. - `FROM`: **_empty_**: Mail from address, RFC 5322. This can be just an email address, or the "Name" \ format. diff --git a/docs/administration/customizing-gitea.md b/docs/administration/customizing-gitea.md index 4af254f8..d364c403 100644 --- a/docs/administration/customizing-gitea.md +++ b/docs/administration/customizing-gitea.md @@ -36,7 +36,7 @@ Application settings can be found in file `CustomConf` which is by default, Again `gitea help` will allow you review this variable and you can override it using the `--config` option on the `gitea` binary. -- [Quick Cheat Sheet](administration/config-cheat-sheet.md) +- [Quick Cheat Sheet](../administration/config-cheat-sheet.md) - [Complete List](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini) If the `CustomPath` folder can't be found despite checking `gitea help`, check the `GITEA_CUSTOM` @@ -44,7 +44,7 @@ environment variable; this can be used to override the default path to something `GITEA_CUSTOM` might, for example, be set by an init script. You can check whether the value is set under the "Configuration" tab on the site administration page. -- [List of Environment Variables](administration/environment-variables.md) +- [List of Environment Variables](../administration/environment-variables.md) :::note Gitea must perform a full restart to see configuration changes. @@ -89,7 +89,7 @@ directory at the top of this document). Every single page of Gitea can be changed. Dynamic content is generated using [go templates](https://pkg.go.dev/html/template), which can be modified by placing replacements below the `$GITEA_CUSTOM/templates` directory. -To obtain any embedded file (including templates), the [`gitea embedded` tool](administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using). +To obtain any embedded file (including templates), the [`gitea embedded` tool](../administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using). Be aware that any statement contained inside `{{` and `}}` are Gitea's template syntax and shouldn't be touched without fully understanding these components. @@ -110,7 +110,7 @@ just place it under your "$GITEA_CUSTOM/public/assets/" directory (for instance To match the current style, the link should have the class name "item", and you can use `{{AppSubUrl}}` to get the base URL: `Impressum` -For more information, see [Adding Legal Pages](administration/adding-legal-pages.md). +For more information, see [Adding Legal Pages](../administration/adding-legal-pages.md). You can add new tabs in the same way, putting them in `extra_tabs.tmpl`. The exact HTML needed to match the style of other tabs is in the file @@ -378,10 +378,10 @@ A full list of supported emoji's is at [emoji list](https://gitea.com/gitea/gite The built-in themes are `gitea-light`, `gitea-dark`, and `gitea-auto` (which automatically adapts to OS settings). -The default theme can be changed via `DEFAULT_THEME` in the [ui](administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. +The default theme can be changed via `DEFAULT_THEME` in the [ui](../administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. Gitea also has support for user themes, which means every user can select which theme should be used. -The list of themes a user can choose from can be configured with the `THEMES` value in the [ui](administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. +The list of themes a user can choose from can be configured with the `THEMES` value in the [ui](../administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. To make a custom theme available to all users: diff --git a/docs/administration/email-setup.md b/docs/administration/email-setup.md index aa88d9be..5f73e64e 100644 --- a/docs/administration/email-setup.md +++ b/docs/administration/email-setup.md @@ -59,7 +59,7 @@ Restart Gitea for the configuration changes to take effect. To send a test email to validate the settings, go to Gitea > Site Administration > Configuration > SMTP Mailer Configuration. -For the full list of options check the [Config Cheat Sheet](administration/config-cheat-sheet.md) +For the full list of options check the [Config Cheat Sheet](../administration/config-cheat-sheet.md) :::note Authentication is only supported when the SMTP server communication is encrypted with TLS or `HOST=localhost`. TLS encryption can be through: diff --git a/docs/administration/external-renderers.md b/docs/administration/external-renderers.md index fec2ab64..8ab1b8d8 100644 --- a/docs/administration/external-renderers.md +++ b/docs/administration/external-renderers.md @@ -24,7 +24,7 @@ it is just a matter of: - add some configuration to your `app.ini` file - restart your Gitea instance -This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](administration/customizing-gitea.md) page. +This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](../administration/customizing-gitea.md) page. ## Installing external binaries diff --git a/docs/administration/fail2ban-setup.md b/docs/administration/fail2ban-setup.md index c90f88c8..0f5ac77b 100644 --- a/docs/administration/fail2ban-setup.md +++ b/docs/administration/fail2ban-setup.md @@ -119,7 +119,7 @@ proxy_set_header X-Real-IP $remote_addr; The security options in `app.ini` need to be adjusted to allow the interpretation of the headers as well as the list of IP addresses and networks that describe trusted proxy servers -(See the [configuration cheat sheet](administration/config-cheat-sheet.md#security-security) for more information). +(See the [configuration cheat sheet](../administration/config-cheat-sheet.md#security-security) for more information). ``` REVERSE_PROXY_LIMIT = 1 diff --git a/docs/administration/https-support.md b/docs/administration/https-support.md index 2587e3f5..afc7a608 100644 --- a/docs/administration/https-support.md +++ b/docs/administration/https-support.md @@ -22,7 +22,7 @@ menu: Before you enable HTTPS, make sure that you have valid SSL/TLS certificates. You could use self-generated certificates for evaluation and testing. Please run `gitea cert --host [HOST]` to generate a self signed certificate. -If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](administration/reverse-proxies.md). +If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](./reverse-proxies.md). To use Gitea's built-in HTTPS support, you must change your `app.ini` file: @@ -36,7 +36,7 @@ KEY_FILE = key.pem ``` Note that if your certificate is signed by a third party certificate authority (i.e. not self-signed), then cert.pem should contain the certificate chain. The server certificate must be the first entry in cert.pem, followed by the intermediaries in order (if any). The root certificate does not have to be included because the connecting client must already have it in order to establish the trust relationship. -To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](./config-cheat-sheet.md#server-server). For the `CERT_FILE` or `KEY_FILE` field, the file path is relative to the `GITEA_CUSTOM` environment variable when it is a relative path. It can be an absolute path as well. @@ -85,11 +85,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](./config-cheat-sheet.md#server-server). ## Using a reverse proxy -Setup up your reverse proxy as shown in the [reverse proxy guide](administration/reverse-proxies.md). +Setup up your reverse proxy as shown in the [reverse proxy guide](../administration/reverse-proxies.md). After that, enable HTTPS by following one of these guides: diff --git a/docs/administration/mail-templates.md b/docs/administration/mail-templates.md index 8e4e416e..1edbd677 100644 --- a/docs/administration/mail-templates.md +++ b/docs/administration/mail-templates.md @@ -18,7 +18,7 @@ menu: # Mail templates To craft the e-mail subject and contents for certain operations, Gitea can be customized by using templates. The templates -for these functions are located under the [`custom` directory](administration/customizing-gitea.md). +for these functions are located under the [`custom` directory](../administration/customizing-gitea.md). Gitea has an internal template that serves as default in case there's no custom alternative. Custom templates are loaded when Gitea starts. Changes made to them are not recognized until Gitea is restarted again. @@ -165,7 +165,7 @@ If the template fails to render, it will be noticed only at the moment the mail A default subject is used if the subject template fails, and whatever was rendered successfully from the _mail body_ is used, disregarding the rest. -Please check [Gitea's logs](administration/logging-config.md) for error messages in case of trouble. +Please check [Gitea's logs](../administration/logging-config.md) for error messages in case of trouble. ## Example diff --git a/docs/administration/repo-indexer.md b/docs/administration/repo-indexer.md index aa822229..be37a8a1 100644 --- a/docs/administration/repo-indexer.md +++ b/docs/administration/repo-indexer.md @@ -25,7 +25,7 @@ Better code search support could be achieved by setting up the repository indexe ## Setting up the repository indexer -Gitea can search through the files of the repositories by enabling this function in your [`app.ini`](administration/config-cheat-sheet.md): +Gitea can search through the files of the repositories by enabling this function in your [`app.ini`](../administration/config-cheat-sheet.md): ```ini [indexer] diff --git a/docs/administration/search-engines-indexation.md b/docs/administration/search-engines-indexation.md index 66494069..0140d68a 100644 --- a/docs/administration/search-engines-indexation.md +++ b/docs/administration/search-engines-indexation.md @@ -23,7 +23,7 @@ If you don't want your repository to be visible for search engines read further. ## Block search engines indexation using robots.txt To make Gitea serve a custom `robots.txt` (default: empty 404) for top level installations, -create a file with path `public/robots.txt` in the [`custom` folder or `CustomPath`](administration/customizing-gitea.md) +create a file with path `public/robots.txt` in the [`custom` folder or `CustomPath`](../administration/customizing-gitea.md) Examples on how to configure the `robots.txt` can be found at [https://moz.com/learn/seo/robotstxt](https://moz.com/learn/seo/robotstxt). diff --git a/docs/development/api-usage.md b/docs/development/api-usage.md index 4fe376b1..59a31d1e 100644 --- a/docs/development/api-usage.md +++ b/docs/development/api-usage.md @@ -19,7 +19,7 @@ menu: ## Enabling/configuring API access -By default, `ENABLE_SWAGGER` is true, and `MAX_RESPONSE_ITEMS` is set to 50. See [Config Cheat Sheet](administration/config-cheat-sheet.md) for more information. +By default, `ENABLE_SWAGGER` is true, and `MAX_RESPONSE_ITEMS` is set to 50. See [Config Cheat Sheet](../administration/config-cheat-sheet.md) for more information. ## Authentication diff --git a/docs/development/hacking-on-gitea.md b/docs/development/hacking-on-gitea.md index eba4da17..e7fceb87 100644 --- a/docs/development/hacking-on-gitea.md +++ b/docs/development/hacking-on-gitea.md @@ -271,7 +271,7 @@ Please note you should use the Swagger 2.0 documentation, not the OpenAPI 3 docu When creating new configuration options, it is not enough to add them to the `modules/setting` files. You should add information to `custom/conf/app.ini` and to the -[configuration cheat sheet](administration/config-cheat-sheet.md) +[configuration cheat sheet](../administration/config-cheat-sheet.md) found in `docs/content/doc/administer/config-cheat-sheet.en-us.md` ### Changing the logo diff --git a/docs/help/faq.md b/docs/help/faq.md index a8082807..6b211137 100644 --- a/docs/help/faq.md +++ b/docs/help/faq.md @@ -86,7 +86,7 @@ https://github.com/loganinak/MigrateGitlabToGogs There are a few places that could make this show incorrectly. -1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](administration/reverse-proxies.md) +1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](../administration/reverse-proxies.md) 2. Make sure you have correctly set `ROOT_URL` in the `server` section of your `app.ini` If certain clone options aren't showing up (HTTP/S or SSH), the following options can be checked in your `app.ini` @@ -99,7 +99,7 @@ If certain clone options aren't showing up (HTTP/S or SSH), the following option This error occurs when the reverse proxy limits the file upload size. -See the [reverse proxy guide](administration/reverse-proxies.md) for a solution with nginx. +See the [reverse proxy guide](../administration/reverse-proxies.md) for a solution with nginx. ## Custom Templates not loading or working incorrectly @@ -109,7 +109,7 @@ The correct path for the template(s) will be relative to the `CustomPath` 1. To find `CustomPath`, look for Custom File Root Path in Site Administration -> Configuration 2. If you are still unable to find a path, the default can be [calculated above](#where-does-gitea-store-what-file) -3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](administration/customizing-gitea.md) page to add your template to the correct location. +3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](../administration/customizing-gitea.md) page to add your template to the correct location. ## Does Gitea have a "GitHub/GitLab pages" feature? @@ -127,7 +127,7 @@ A "login prohibited" user is a user that is not allowed to log in to Gitea anymo ## Setting up logging -- [Official Docs](administration/logging-config.md) +- [Official Docs](../administration/logging-config.md) ## What is Swagger? @@ -150,7 +150,7 @@ There are multiple things you can combine to prevent spammers. 1. By whitelisting or blocklisting certain email domains 2. By only whitelisting certain domains with OpenID (see below) 3. Setting `ENABLE_CAPTCHA` to `true` in your `app.ini` and properly configuring `RECAPTCHA_SECRET` and `RECAPTCHA_SITEKEY` -4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI +4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](../administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI ### Only allow/block certain email domains @@ -178,7 +178,7 @@ At some point, a customer or third party needs access to a specific repo and onl ### Enable Fail2ban -Use [Fail2Ban](administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns +Use [Fail2Ban](../administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns ## SSHD vs built-in SSH @@ -322,24 +322,24 @@ You may want to set this value to `60m` or `120m`. ## How can I create users before starting Gitea -Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](administration/command-line.md#admin) to add users like normal. +Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](../administration/command-line.md#admin) to add users like normal. ## How can I enable password reset -There is no setting for password resets. It is enabled when a [mail service](administration/email-setup.md) is configured, and disabled otherwise. +There is no setting for password resets. It is enabled when a [mail service](../administration/email-setup.md) is configured, and disabled otherwise. ## How can a user's password be changed - As an **admin**, you can change any user's password (and optionally force them to change it on next login)... - By navigating to your `Site Administration -> User Accounts` page and editing a user. - - By using the [admin CLI commands](administration/command-line.md#admin). + - By using the [admin CLI commands](../administration/command-line.md#admin). - Keep in mind most commands will also need a [global flag](administration/command-line.md#global-options) to point the CLI at the correct configuration. + Keep in mind most commands will also need a [global flag](../administration/command-line.md#global-options) to point the CLI at the correct configuration. - As a **user** you can change it... - In your account `Settings -> Account` page (this method **requires** you to know your current password). - By using the `Forgot Password` link. - If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](administration/email-setup.md). + If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](../administration/email-setup.md). ## Why is my markdown broken @@ -417,9 +417,9 @@ It is highly recommended to back-up your database before running these commands. - You can also check `/admin/config` for the repository root path. - Ensure that the user/org exists that you want to adopt repositories for. - As an admin, go to `/admin/repos/unadopted` and search. - - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository). + - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository). - If the above steps are done correctly, you should be able to select repositories to adopt. - - If no repositories are found, enable [debug logging](administration/config-cheat-sheet.md#repository) to check for any specific errors. + - If no repositories are found, enable [debug logging](../administration/config-cheat-sheet.md#repository-repository) to check for any specific errors. ## Gitea can't start on NFS diff --git a/docs/index.md b/docs/index.md index 73dc86d6..f2f3752c 100644 --- a/docs/index.md +++ b/docs/index.md @@ -15,7 +15,7 @@ blog post to read about the justification for a fork. :::warning -Gitea has never sent commits to upstream or cherry-pick commits from upstream. So Gitea is totally not compatible with Gogs. No any gurantee it can work if you upgrade from Gogs to Gitea. The recommands method is to migrate repositories from Gogs to Gitea. +Gitea has never sent commits to upstream or cherry-pick commits from upstream. So Gitea is totally not compatible with Gogs. No any gurantee it can work if you upgrade from Gogs to Gitea. The recommanded method is to migrate repositories from Gogs to Gitea. ::: diff --git a/docs/installation/comparison.md b/docs/installation/comparison.md index fdb8c3bc..aab6a4c2 100644 --- a/docs/installation/comparison.md +++ b/docs/installation/comparison.md @@ -88,7 +88,7 @@ _Symbols used in table:_ | Visual comparison of image changes | ✓ | ✘ | ✓ | ? | ? | ? | ✘ | ✘ | - Gitea has builtin repository-level code search -- Better code search support could be achieved by [using a repository indexer](administration/repo-indexer.md) +- Better code search support could be achieved by [using a repository indexer](../administration/repo-indexer.md) ## Issue Tracker diff --git a/docs/installation/from-binary.md b/docs/installation/from-binary.md index dda08aa8..5169588d 100644 --- a/docs/installation/from-binary.md +++ b/docs/installation/from-binary.md @@ -65,7 +65,7 @@ despite warnings like `This key is not certified with a trusted signature!`. ## Recommended server configuration :::note -Many of the following directories can be configured using [Environment Variables](administration/environment-variables.md) as well! +Many of the following directories can be configured using [Environment Variables](../administration/environment-variables.md) as well! Of note, configuring `GITEA_WORK_DIR` will tell Gitea where to base its working directory, as well as ease installation. ::: @@ -130,7 +130,7 @@ If you don't want the web installer to be able to write to the config file, it i * Ensure that the `SECRET_KEY` and `INTERNAL_TOKEN` values are set. (You may want to use the `gitea generate secret` to generate these secret keys.) * Ensure that any other secret keys you need are set. -See the [command line documentation](administration/command-line.md) for information on using `gitea generate secret`. +See the [command line documentation](../administration/command-line.md) for information on using `gitea generate secret`. ### Configure Gitea's working directory @@ -177,7 +177,7 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini You can update to a new version of Gitea by stopping Gitea, replacing the binary at `/usr/local/bin/gitea` and restarting the instance. The binary file name should not be changed during the update to avoid problems in existing repositories. -It is recommended that you make a [backup](administration/backup-and-restore.md) before updating your installation. +It is recommended that you make a [backup](../administration/backup-and-restore.md) before updating your installation. If you have carried out the installation steps as described above, the binary should have the generic name `gitea`. Do not change this, i.e. to include the version number. diff --git a/docs/installation/with-docker-rootless.md b/docs/installation/with-docker-rootless.md index df287c55..ddd5d8e0 100644 --- a/docs/installation/with-docker-rootless.md +++ b/docs/installation/with-docker-rootless.md @@ -256,7 +256,7 @@ documented above, please note that `db` must be used as the database hostname. ## Customization -Customization files described [here](administration/customizing-gitea.md) should +Customization files described [here](../administration/customizing-gitea.md) should be placed in `/var/lib/gitea/custom` directory. If using host volumes, it's quite easy to access these files; for named volumes, this is done through another container or by direct access at `/var/lib/docker/volumes/gitea_gitea/_/var_lib_gitea`. The configuration file will be saved at @@ -317,7 +317,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -To set required TOKEN and SECRET values, consider using Gitea's built-in [generate utility functions](administration/command-line.md#generate). +To set required TOKEN and SECRET values, consider using Gitea's built-in [generate utility functions](../administration/command-line.md#generate). # SSH Container Passthrough @@ -346,7 +346,7 @@ Once the wrapper is in place, you can make it the shell for the `git` user: sudo usermod -s /usr/local/bin/gitea-shell git ``` -Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the [SSH AuthorizedKeysCommand](administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: +Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: ```bash Match User git diff --git a/docs/installation/with-docker.md b/docs/installation/with-docker.md index cd81ab43..5b3e5c1f 100644 --- a/docs/installation/with-docker.md +++ b/docs/installation/with-docker.md @@ -263,7 +263,7 @@ documented above, please note that `db` must be used as the database hostname. ## Customization -Customization files described [here](administration/customizing-gitea.md) should +Customization files described [here](../administration/customizing-gitea.md) should be placed in `/data/gitea` directory. If using host volumes, it's quite easy to access these files; for named volumes, this is done through another container or by direct access at `/var/lib/docker/volumes/gitea_gitea/_data`. The configuration file will be saved at @@ -314,7 +314,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -Gitea will generate new secrets/tokens for every new installation automatically and write them into the app.ini. If you want to set the secrets/tokens manually, you can use the following docker commands to use of Gitea's built-in [generate utility functions](administration/command-line.md#generate). Do not lose/change your SECRET_KEY after the installation, otherwise the encrypted data can not be decrypted anymore. +Gitea will generate new secrets/tokens for every new installation automatically and write them into the app.ini. If you want to set the secrets/tokens manually, you can use the following docker commands to use of Gitea's built-in [generate utility functions](../administration/command-line.md#generate). Do not lose/change your SECRET_KEY after the installation, otherwise the encrypted data can not be decrypted anymore. The following commands will output a new `SECRET_KEY` and `INTERNAL_TOKEN` to `stdout`, which you can then place in your environment variables. @@ -558,7 +558,7 @@ In this option, the idea is that the host SSH uses an `AuthorizedKeysCommand` in Now all attempts to login as the `git` user on the host will be forwarded to the docker - including the `SSH_ORIGINAL_COMMAND`. We now need to set-up SSH authentication on the host. -We will do this by leveraging the [SSH AuthorizedKeysCommand](administration/command-line.md#keys) to match the keys against those accepted by Gitea. +We will do this by leveraging the [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: diff --git a/docs/search.md b/docs/search.md deleted file mode 100644 index 226d9fe3..00000000 --- a/docs/search.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -date: "2019-11-12T16:00:00+02:00" -title: "Search" -slug: "search" -sidebar_position: 1 -toc: false -draft: false -aliases: - - /en-us/help/search -sitemap: - priority : 1 -layout: "search" ---- - -This file exists solely to respond to /search URL with the related `search` layout template. - -No content shown here is rendered, all content is based in the template layouts/doc/search.html - -Setting a very low sitemap priority will tell search engines this is not important content. diff --git a/docs/usage/actions/act-runner.md b/docs/usage/actions/act-runner.md index 942d1269..c51e920b 100644 --- a/docs/usage/actions/act-runner.md +++ b/docs/usage/actions/act-runner.md @@ -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.md#actions-generate-runner-token): +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 diff --git a/docs/usage/actions/comparison.md b/docs/usage/actions/comparison.md index 5b084e09..4af66960 100644 --- a/docs/usage/actions/comparison.md +++ b/docs/usage/actions/comparison.md @@ -136,7 +136,7 @@ If you want to download an action from another git hoster, you can use an absolu If your Gitea instance is in an intranet or a restricted area, you can set the URL to `self` to only download actions from your own instance by default. Of course, you can still use absolute URLs in workflows. -More details about the `[actions].DEFAULT_ACTIONS_URL` configuration can be found in the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions)。 +More details about the `[actions].DEFAULT_ACTIONS_URL` configuration can be found in the [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions)。 ### Context availability diff --git a/docs/usage/actions/faq.md b/docs/usage/actions/faq.md index 74eb0654..7d4804cc 100644 --- a/docs/usage/actions/faq.md +++ b/docs/usage/actions/faq.md @@ -62,7 +62,7 @@ This is one of the differences from GitHub Actions which supports actions script But it should allow users much more flexibility in how they run Actions. Alternatively, if you want your runners to download actions from your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`. -See [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions). +See [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions). ## How to limit the permission of the runners? diff --git a/docs/usage/actions/quickstart.md b/docs/usage/actions/quickstart.md index 0514b6dd..e6e3a503 100644 --- a/docs/usage/actions/quickstart.md +++ b/docs/usage/actions/quickstart.md @@ -30,7 +30,7 @@ Since 1.21.0, Actions are enabled by default. If you are using versions before 1 ENABLED=true ``` -If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions). +If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions). ### Set up runner @@ -129,7 +129,7 @@ That is because Gitea Actions is designed to be compatible with GitHub Actions Be careful, the demo file contains some emojis. Please make sure your database supports them, especially when using MySQL. If the charset is not `utf8mb4`, errors will occur, such as `Error 1366 (HY000): Incorrect string value: '\\xF0\\x9F\\x8E\\x89 T...' for column 'name' at row 1`. -See [Database Preparation](installation/database-preparation.md#mysql) for more information. +See [Database Preparation](../../installation/database-preparation.md#mysqlmariadb) for more information. Alternatively, you can remove all emojis from the demo file and try again. diff --git a/docs/usage/labels.md b/docs/usage/labels.md index 4058ca14..670e7756 100644 --- a/docs/usage/labels.md +++ b/docs/usage/labels.md @@ -27,7 +27,7 @@ For organizations, you can define organization-wide labels that are shared with Labels have a mandatory name, a mandatory color, an optional description, and must either be exclusive or not (see `Scoped Labels` below). -When you create a repository, you can ensure certain labels exist by using the `Issue Labels` option. This option lists a number of available label sets that are [configured globally on your instance](../administration/customizing-gitea/#labels). Its contained labels will all be created as well while creating the repository. +When you create a repository, you can ensure certain labels exist by using the `Issue Labels` option. This option lists a number of available label sets that are [configured globally on your instance](../administration/customizing-gitea.md#labels). Its contained labels will all be created as well while creating the repository. ## Scoped Labels diff --git a/docs/usage/linked-references.md b/docs/usage/linked-references.md index 440727b4..e5c28abb 100644 --- a/docs/usage/linked-references.md +++ b/docs/usage/linked-references.md @@ -94,7 +94,7 @@ Sometimes a commit or pull request may fix or bring back a problem documented in a particular issue. Gitea supports closing and reopening the referenced issues by preceding the reference with a particular _keyword_. Common keywords include "closes", "fixes", "reopens", etc. This list can be -[customized](administration/config-cheat-sheet.md) by the +[customized](../administration/config-cheat-sheet.md) by the site administrator. Example: diff --git a/docs/usage/packages/storage.md b/docs/usage/packages/storage.md index f437412d..3db44aaa 100644 --- a/docs/usage/packages/storage.md +++ b/docs/usage/packages/storage.md @@ -28,7 +28,7 @@ Whenever a package gets deleted, only the references to the underlying blobs are The blobs get not removed at this moment, so they still require space on the filesystem. When a new package gets uploaded the existing blobs may get referenced again. -These unreferenced blobs get deleted by a [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages). +These unreferenced blobs get deleted by a [clean up job](../../administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages). The config setting `OLDER_THAN` configures how long unreferenced blobs are kept before they get deleted. ## Cleanup Rules @@ -68,7 +68,7 @@ The patterns are case-insensitive which matches the behaviour of the package reg ### How the cleanup rules work -The cleanup rules are part of the [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically. +The cleanup rules are part of the [clean up job](../../administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically. The cleanup rule: diff --git a/docs/usage/push.md b/docs/usage/push.md index d88dc1a2..a8c87a46 100644 --- a/docs/usage/push.md +++ b/docs/usage/push.md @@ -51,7 +51,7 @@ Push to create is a feature that allows you to push to a repository that does no ## Enabling Push To Create -In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#repository-repository). +In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](../administration/config-cheat-sheet.md#repository-repository). ## Using Push To Create diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/cmd-embedded.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/cmd-embedded.md index a2df1aa2..c799911b 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/cmd-embedded.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/cmd-embedded.md @@ -17,7 +17,7 @@ menu: # 嵌入资源提取工具 -Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](administration/customizing-gitea.md)）。 +Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](../administration/customizing-gitea.md)）。 要获取嵌入资源的副本以进行编辑，可以使用 CLI 中的 `embedded` 命令，通过操作系统的 shell 执行。 @@ -71,7 +71,7 @@ gitea [--config {file}] embedded extract [--destination {dir}|--custom] [--overw `--destination` 选项用于指定提取文件的目标目录。默认为当前目录。 -`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md)。 +`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](../administration/customizing-gitea.md)。 `--overwrite` 标志允许覆盖目标目录中的任何现有文件。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/config-cheat-sheet.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/config-cheat-sheet.md index e9905c4b..7b1cf42f 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/config-cheat-sheet.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/config-cheat-sheet.md @@ -693,7 +693,7 @@ Gitea 创建以下非唯一队列： - `FORCE_TRUST_SERVER_CERT`: **false**：如果设置为 `true`，将完全忽略服务器证书验证错误。此选项不安全。考虑将证书添加到系统信任存储中。 - `USER`: **_empty_**：邮件用户的用户名（通常是发件人的电子邮件地址）。 - `PASSWD`: **_empty_**：邮件用户的密码。如果密码中使用了特殊字符，请使用 \`your password\` 进行引用。 - - 请注意：只有在 SMTP 服务器通信通过 TLS 加密（可以通过 `STARTTLS` 实现）或 SMTP 主机是 localhost 时，才支持身份验证。有关更多信息，请参阅 [邮件设置](administration/email-setup.md)。 + - 请注意：只有在 SMTP 服务器通信通过 TLS 加密（可以通过 `STARTTLS` 实现）或 SMTP 主机是 localhost 时，才支持身份验证。有关更多信息，请参阅 [邮件设置](../administration/email-setup.md)。 - `ENABLE_HELO`: **true**：启用 HELO 操作。 - `HELO_HOSTNAME`: **（从系统检索）**：HELO 主机名。 - `FROM`: **_empty_**：邮件的发件人地址，符合 RFC 5322。这可以是一个电子邮件地址，也可以是 "Name" \ 格式。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/customizing-gitea.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/customizing-gitea.md index f41533c6..0ebc0703 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/customizing-gitea.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/customizing-gitea.md @@ -23,13 +23,13 @@ Gitea 引用 `custom` 目录中的自定义配置文件来覆盖配置、模板 将会自动创建包括 `custom/` 在内的必要应用目录，应用本身的配置存放在 `custom/conf/app.ini` 当中。在发行版中可能会以 `/etc/gitea/` 的形式为 `custom` 设置一个符号链接，查看配置详情请移步： -- [快速备忘单](administration/config-cheat-sheet.md) +- [快速备忘单](../administration/config-cheat-sheet.md) - [完整配置清单](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini) 如果您在 binary 同目录下无法找到 `custom` 文件夹，请检查您的 `GITEA_CUSTOM` 环境变量配置， 因为它可能被配置到了其他地方（可能被一些启动脚本设置指定了目录）。 -- [环境变量清单](administration/environment-variables.md) +- [环境变量清单](../administration/environment-variables.md) **注：** 必须完全重启 Gitea 以使配置生效。 @@ -88,4 +88,4 @@ Gitea 引用 `custom` 目录中的自定义配置文件来覆盖配置、模板 内置主题是“gitea-light”、“gitea-dark”和“gitea-auto”（自动适应操作系统设置）。 -默认主题可以通过 `app.ini` 的 [ui](administration/config-cheat-sheet.md#ui-ui) 部分中的 `DEFAULT_THEME` 进行更改。 +默认主题可以通过 `app.ini` 的 [ui](../administration/config-cheat-sheet.md#ui-ui) 部分中的 `DEFAULT_THEME` 进行更改。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/email-setup.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/email-setup.md index 7d99a5ca..4d9faa5e 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/email-setup.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/email-setup.md @@ -55,7 +55,7 @@ PASSWD = `password` 要发送测试邮件以验证设置，请转到 Gitea > 站点管理 > 配置 > SMTP 邮件配置。 -有关所有选项的完整列表，请查看[配置速查表](administration/config-cheat-sheet.md)。 +有关所有选项的完整列表，请查看[配置速查表](../administration/config-cheat-sheet.md)。 请注意：只有在使用 TLS 或 `HOST=localhost` 加密 SMTP 服务器通信时才支持身份验证。TLS 加密可以通过以下方式进行： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/external-renderers.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/external-renderers.md index 1e56d95a..e6c6d116 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/external-renderers.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/external-renderers.md @@ -23,7 +23,7 @@ Gitea 通过外部二进制文件支持自定义文件渲染（例如 Jupyter no - 在您的 `app.ini` 文件中添加一些配置 - 重新启动 Gitea 实例 -此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md) 页面上的一些示例。 +此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](../administration/customizing-gitea.md) 页面上的一些示例。 ## 安装外部二进制文件 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/fail2ban-setup.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/fail2ban-setup.md index 457afba9..a70ed988 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/fail2ban-setup.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/fail2ban-setup.md @@ -91,4 +91,4 @@ REVERSE_PROXY_TRUSTED_PROXIES = 127.0.0.0/8,::1/128 `REVERSE_PROXY_LIMIT` 限制反向代理服务器的层数，设置为 `0` 表示不使用这些标头。 `REVERSE_PROXY_TRUSTED_PROXIES` 表示受信任的反向代理服务器网络地址， 经过该网络地址转发来的流量会经过解析 `X-Real-IP` 头部得到真实客户端地址。 -（参考 [configuration cheat sheet](administration/config-cheat-sheet.md#security-security)） +（参考 [configuration cheat sheet](../administration/config-cheat-sheet.md#security-security)） diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/https-support.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/https-support.md index 8beb06e8..815f3295 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/https-support.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/https-support.md @@ -20,7 +20,7 @@ menu: 在启用HTTPS之前，确保您拥有有效的SSL/TLS证书。 建议在测试和评估情况下使用自签名证书，请运行 `gitea cert --host [HOST]` 以生成自签名证书 -如果您在服务器上使用阿帕奇（Apache）或Nginx，建议参考 [反向代理指南](administration/reverse-proxies.md)。 +如果您在服务器上使用阿帕奇（Apache）或Nginx，建议参考 [反向代理指南](../administration/reverse-proxies.md)。 要使用Gitea内置HTTPS支持，您必须编辑`app.ini`文件。 @@ -33,7 +33,7 @@ CERT_FILE = cert.pem KEY_FILE = key.pem ``` -请注意，如果您的证书由第三方证书颁发机构签名（即不是自签名的），则 cert.pem 应包含证书链。服务器证书必须是 cert.pem 中的第一个条目，后跟中介（如果有）。不必包含根证书，因为连接客户端必须已经拥有根证书才能建立信任关系。要了解有关配置值的更多信息，请查看 [配置备忘单](administration/config-cheat-sheet#server-server)。 +请注意，如果您的证书由第三方证书颁发机构签名（即不是自签名的），则 cert.pem 应包含证书链。服务器证书必须是 cert.pem 中的第一个条目，后跟中介（如果有）。不必包含根证书，因为连接客户端必须已经拥有根证书才能建立信任关系。要了解有关配置值的更多信息，请查看 [配置备忘单](../administration/config-cheat-sheet#server-server)。 对于“CERT_FILE”或“KEY_FILE”字段，当文件路径是相对路径时，文件路径相对于“GITEA_CUSTOM”环境变量。它也可以是绝对路径。 @@ -82,11 +82,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -要了解关于配置, 请访问 [配置备忘单](administration/config-cheat-sheet.md#server-server)获取更多信息 +要了解关于配置, 请访问 [配置备忘单](../administration/config-cheat-sheet.md#server-server)获取更多信息 ## 使用反向代理服务器 -按照 [reverse proxy guide](administration/reverse-proxies.md) 的规则设置你的反向代理服务器 +按照 [reverse proxy guide](../administration/reverse-proxies.md) 的规则设置你的反向代理服务器 然后，按照下面的向导启用 HTTPS： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/mail-templates.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/mail-templates.md index 3c7c2a93..25da3105 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/mail-templates.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/mail-templates.md @@ -17,7 +17,7 @@ menu: # 邮件模板 -为了定制特定操作的电子邮件主题和内容，可以使用模板来自定义 Gitea。这些功能的模板位于 [`custom` 目录](administration/customizing-gitea.md) 下。 +为了定制特定操作的电子邮件主题和内容，可以使用模板来自定义 Gitea。这些功能的模板位于 [`custom` 目录](../administration/customizing-gitea.md) 下。 如果没有自定义的替代方案，Gitea 将使用内部模板作为默认模板。 自定义模板在 Gitea 启动时加载。对它们的更改在 Gitea 重新启动之前不会被识别。 @@ -148,7 +148,7 @@ _主题_ 和 _邮件正文_ 由 [Golang的模板引擎](https://go.dev/pkg/text/ 如果模板无法呈现，则只有在发送邮件时才会注意到。 如果主题模板失败，将使用默认主题，如果从 _邮件正文_ 中成功呈现了任何内容，则将使用该内容，忽略其他内容。 -如果遇到问题，请检查 [Gitea的日志](administration/logging-config.md) 以获取错误消息。 +如果遇到问题，请检查 [Gitea的日志](../administration/logging-config.md) 以获取错误消息。 ## 示例 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/repo-indexer.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/repo-indexer.md index d70a617a..5c394642 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/repo-indexer.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/administration/repo-indexer.md @@ -19,7 +19,7 @@ menu: ## 设置仓库索引器 -通过在您的 [`app.ini`](administration/config-cheat-sheet.md) 中启用此功能，Gitea 可以通过仓库的文件进行搜索： +通过在您的 [`app.ini`](../administration/config-cheat-sheet.md) 中启用此功能，Gitea 可以通过仓库的文件进行搜索： ```ini [indexer] diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/development/api-usage.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/development/api-usage.md index d7aca16f..6428660b 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/development/api-usage.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/development/api-usage.md @@ -19,7 +19,7 @@ menu: ## 开启/配置 API 访问 -通常情况下， `ENABLE_SWAGGER` 默认开启并且参数 `MAX_RESPONSE_ITEMS` 默认为 50。您可以从 [Config Cheat Sheet](administration/config-cheat-sheet.md) 中获取更多配置相关信息。 +通常情况下， `ENABLE_SWAGGER` 默认开启并且参数 `MAX_RESPONSE_ITEMS` 默认为 50。您可以从 [Config Cheat Sheet](../administration/config-cheat-sheet.md) 中获取更多配置相关信息。 ## 通过 API 认证 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/development/hacking-on-gitea.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/development/hacking-on-gitea.md index 7dfea305..1cae90c3 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/development/hacking-on-gitea.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/development/hacking-on-gitea.md @@ -245,7 +245,7 @@ make swagger-check ### 创建新的配置选项 创建新的配置选项时，将它们添加到 `modules/setting` 的对应文件。您应该将信息添加到 `custom/conf/app.ini` -并到[配置备忘单](administration/config-cheat-sheet.md) +并到[配置备忘单](../administration/config-cheat-sheet.md) 在 `docs/content/doc/advanced/config-cheat-sheet.zh-cn.md` 中找到 ### 更改Logo diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/faq.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/faq.md index d24dfe24..44d01e44 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/faq.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/help/faq.md @@ -87,7 +87,7 @@ https://github.com/loganinak/MigrateGitlabToGogs 有几个地方可能会导致显示不正确。 -1. 如果使用反向代理，请确保按照[反向代理指南](administration/reverse-proxies.md)中的正确说明进行设置。 +1. 如果使用反向代理，请确保按照[反向代理指南](../administration/reverse-proxies.md)中的正确说明进行设置。 2. 确保在`app.ini`的`server`部分中正确设置了`ROOT_URL`。 如果某些克隆选项未显示（HTTP/S或SSH），可以在`app.ini中` @@ -100,7 +100,7 @@ https://github.com/loganinak/MigrateGitlabToGogs 当反向代理限制文件上传大小时，会出现此错误。 -有关使用nginx解决此问题，请参阅[反向代理指南](administration/reverse-proxies.md)。 +有关使用nginx解决此问题，请参阅[反向代理指南](../administration/reverse-proxies.md)。 ## 自定义模板无法加载或运行错误 @@ -113,7 +113,7 @@ Gitea的自定义模板必须将其添加到正确的位置，否则Gitea将无 如果找不到，请尝试`echo $GITEA_CUSTOM`。 2. 如果仍然找不到，默认值可以被[计算](help/faq.md#where-does-gitea-store-what-file) -3. 如果仍然找不到路径，则可以参考[自定义Gitea](administration/customizing-gitea.md)页面，将模板添加到正确的位置。 +3. 如果仍然找不到路径，则可以参考[自定义Gitea](../administration/customizing-gitea.md)页面，将模板添加到正确的位置。 ## Gitea是否有"GitHub/GitLab Pages"功能？ @@ -131,7 +131,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 ## 设置日志记录 -- [官方文档](administration/logging-config.md) +- [官方文档](../administration/logging-config.md) ## 什么是Swagger？ @@ -154,7 +154,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 1. 通过设置电子邮件域名的白名单或黑名单。 2. 通过设置一些域名或者OpenID白名单（见下文）。 3. 在您的`app.ini`中将`ENABLE_CAPTCHA`设置为`true`，并正确配置`RECAPTCHA_SECRET`和 `RECAPTCHA_SITEKEY`。 -4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。 +4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](../administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。 ### 仅允许/阻止特定的电子邮件域名 @@ -180,7 +180,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 ### 启用 Fail2ban -使用 [Fail2Ban](administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。 +使用 [Fail2Ban](../administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。 ## SSHD vs 内建SSH @@ -324,24 +324,24 @@ error: failed to push some refs to '' ## 如何在启动 Gitea 之前创建用户 -Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](administration/command-line.md#admin)像正常情况下添加用户。 +Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](../administration/command-line.md#admin)像正常情况下添加用户。 ## 如何启用密码重置 -没有密码重置的设置。当配置了[邮件服务](administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。 +没有密码重置的设置。当配置了[邮件服务](../administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。 ## 如何更改用户的密码 - 作为管理员，您可以更改任何用户的密码（并可选择强制其在下次登录时更改密码）... - 转到您的`站点管理 -> 用户账户`页面并编辑用户。 -- 使用[管理 CLI 命令](administration/command-line.md#admin)。 +- 使用[管理 CLI 命令](../administration/command-line.md#admin)。 - 请注意，大多数命令还需要一个[全局标志](administration/command-line.md#global-options)来指向正确的配置。 + 请注意，大多数命令还需要一个[全局标志](../administration/command-line.md#global-options)来指向正确的配置。 - 作为**用户**，您可以更改密码... - 在您的账户的`设置 -> 账户`页面（此方法**需要**您知道当前密码）。 - 使用`忘记密码`链接。 - 如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](administration/email-setup.md)。 + 如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](../administration/email-setup.md)。 ## 为什么我的 Markdown 显示错误 @@ -433,6 +433,6 @@ gitea doctor recreate-table - 您还可以在`/admin/config`中检查存储库根路径。 - 确保存在要采用存储库的用户/组织。 - 作为管理员，转到`/admin/repos/unadopted`并搜索。 -- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository) 获得类似的权限。 +- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository) 获得类似的权限。 - 如果上述步骤都正确执行，您应该能够选择要采用的存储库。 - - 如果没有找到存储库，请启用[调试日志记录](administration/config-cheat-sheet.md#repository)以检查是否有特定错误。 + - 如果没有找到存储库，请启用[调试日志记录](../administration/config-cheat-sheet.md#repository-repository)以检查是否有特定错误。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/from-binary.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/from-binary.md index 216a6be5..069f6338 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/from-binary.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/from-binary.md @@ -57,7 +57,7 @@ gpg --verify gitea-@version@-linux-amd64.asc gitea-@version@-linux-amd64 ## 服务器设置 -**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](administration/environment-variables.md) 初始化。 +**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](../administration/environment-variables.md) 初始化。 ### 准备环境 @@ -117,7 +117,7 @@ chmod 770 /etc/gitea - 使用 `gitea generate secret` 创建 `SECRET_KEY` 和 `INTERNAL_TOKEN` - 提供所有必要的密钥 -详情参考 [命令行文档](administration/command-line.md) 中有关 `gitea generate secret` 的内容。 +详情参考 [命令行文档](../administration/command-line.md) 中有关 `gitea generate secret` 的内容。 ### 配置 Gitea 工作路径 @@ -159,7 +159,7 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini 您可以通过停止程序，替换 `/usr/local/bin/gitea` 并重启来更新到新版本。直接替换可执行程序时不要更改或使用新的文件名称，以避免数据出错。 -建议您在更新之前进行[备份](administration/backup-and-restore.md)。 +建议您在更新之前进行[备份](../administration/backup-and-restore.md)。 如果您按照上述描述执行了安装步骤，二进制文件的通用名称应为 gitea。请勿更改此名称，即不要包含版本号。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/with-docker-rootless.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/with-docker-rootless.md index d2888cbd..2432adf5 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/with-docker-rootless.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/with-docker-rootless.md @@ -283,7 +283,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -要设置所需的 TOKEN 和 SECRET 值，可以使用 Gitea 的内置[生成使用函数](administration/command-line.md#generate). +要设置所需的 TOKEN 和 SECRET 值，可以使用 Gitea 的内置[生成使用函数](../administration/command-line.md#generate). # SSH 容器透传 @@ -312,7 +312,7 @@ sudo chmod +x /usr/local/bin/gitea-shell sudo usermod -s /usr/local/bin/gitea-shell git ``` -现在，所有的 SSH 命令都会被转发到容器，您需要在主机上设置 SSH 认证。这可以通过利用 [SSH AuthorizedKeysCommand](administration/command-line.md#keys) 来匹配 Gitea 接受的密钥。在主机的 `/etc/ssh/sshd_config` 文件中添加以下代码块： +现在，所有的 SSH 命令都会被转发到容器，您需要在主机上设置 SSH 认证。这可以通过利用 [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) 来匹配 Gitea 接受的密钥。在主机的 `/etc/ssh/sshd_config` 文件中添加以下代码块： ```bash Match User git diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/with-docker.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/with-docker.md index 77ac6ab2..fcbd7016 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/with-docker.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/installation/with-docker.md @@ -260,7 +260,7 @@ MySQL 或 PostgreSQL 容器将需要分别创建。 ## 自定义 -[此处](administration/customizing-gitea.md)描述的定制文件应放在 `/data/gitea` 目录中。如果使用主机卷，则访问这些文件非常容易；对于命名卷，可以通过另一个容器或通过直接访问 `/var/lib/docker/volumes/gitea_gitea/_data` 来完成。安装后，配置文件将保存在 `/data/gitea/conf/app.ini` 中。 +[此处](../administration/customizing-gitea.md)描述的定制文件应放在 `/data/gitea` 目录中。如果使用主机卷，则访问这些文件非常容易；对于命名卷，可以通过另一个容器或通过直接访问 `/var/lib/docker/volumes/gitea_gitea/_data` 来完成。安装后，配置文件将保存在 `/data/gitea/conf/app.ini` 中。 ## 升级 @@ -295,7 +295,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -Gitea 将为每次新安装自动生成新的 `SECRET_KEY` 并将它们写入 `app.ini`。 如果您想手动设置 `SECRET_KEY`，您可以使用以下 docker 命令来使用 Gitea 内置的[方法](administration/command-line.md#generate)生成 `SECRET_KEY`。 安装后请妥善保管您的 `SECRET_KEY`，如若丢失则无法解密已加密的数据。 +Gitea 将为每次新安装自动生成新的 `SECRET_KEY` 并将它们写入 `app.ini`。 如果您想手动设置 `SECRET_KEY`，您可以使用以下 docker 命令来使用 Gitea 内置的[方法](../administration/command-line.md#generate)生成 `SECRET_KEY`。 安装后请妥善保管您的 `SECRET_KEY`，如若丢失则无法解密已加密的数据。 以下命令将向 `stdout` 输出一个新的 `SECRET_KEY` 和 `INTERNAL_TOKEN`，然后您可以将其放入环境变量中。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/search.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/search.md deleted file mode 100644 index 6ab5ad08..00000000 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/search.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -date: "2019-11-12T16:00:00+02:00" -title: "搜索" -slug: "search" -sidebar_position: 1 -toc: false -draft: false -aliases: - - /zh-cn/help/search -sitemap: - priority : 1 -layout: "search" ---- - -This file exists solely to respond to /search URL with the related `search` layout template. - -No content shown here is rendered, all content is based in the template layouts/doc/search.html - -Setting a very low sitemap priority will tell search engines this is not important content. diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/act-runner.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/act-runner.md index e5ebff97..4541a1b1 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/act-runner.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/act-runner.md @@ -113,7 +113,7 @@ Runner级别决定了从哪里获取注册令牌。 注册令牌的格式是一个随机字符串 `D0gvfu2iHfUjNqCYVljVyRV14fISpJxxxxxxxxxx`。 -注册令牌也可以通过 Gitea 的 [命令行](administration/command-line.md#actions-generate-runner-token) 获得: +注册令牌也可以通过 Gitea 的 [命令行](../../administration/command-line.md#actions-generate-runner-token) 获得: ### 注册Runner diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/comparison.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/comparison.md index 79450e8e..fdb96ceb 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/comparison.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/comparison.md @@ -132,7 +132,7 @@ Gitea Actions目前不支持此功能。 如果你的 Gitea 实例是部署在一个互联网限制的网络中，也可以使用绝对地址来下载 actions。你也可以将配置项修改为 `[actions].DEFAULT_ACTIONS_URL = self`。这样所有的相对路径的actions引用，将不再会从 github.com 去下载，而会从这个 Gitea 实例自己的仓库中去下载。例如： `uses: actions/checkout@v4` 将会从 `[server].ROOT_URL`/actions/checkout.git 这个地址去下载 actions。 -设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单](administration/config-cheat-sheet.md#actions-actions)。 +设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单](../../administration/config-cheat-sheet.md#actions-actions)。 ### 上下文可用性 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/faq.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/faq.md index 48fc3272..112fe51b 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/faq.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/faq.md @@ -63,7 +63,7 @@ GitHub 上有成千上万个 [Actions 脚本](https://github.com/marketplace?typ 但用户理应拥有权利去灵活决定如何运行 Actions。 另外，如果您希望您的 Runner 默认从您自己的 Gitea 实例下载 Actions，可以通过设置 `[actions].DEFAULT_ACTIONS_URL`进行配置。 -参见[配置速查表](administration/config-cheat-sheet.md#actions-actions)。 +参见[配置速查表](../../administration/config-cheat-sheet.md#actions-actions)。 ## 如何限制Runner的权限？ diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/quickstart.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/quickstart.md index 8fccc6c9..e94672cd 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/quickstart.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/actions/quickstart.md @@ -30,7 +30,7 @@ menu: ENABLED=true ``` -如果您想了解更多信息或在配置过程中遇到任何问题，请参考[配置速查表](administration/config-cheat-sheet.md#actions-actions)。 +如果您想了解更多信息或在配置过程中遇到任何问题，请参考[配置速查表](../../administration/config-cheat-sheet.md#actions-actions)。 ### 设置Runner diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/labels.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/labels.md index b9cf3930..746bf6bb 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/labels.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/labels.md @@ -27,7 +27,7 @@ menu: 标签具有必填的名称和颜色，可选的描述，以及必须是独占的或非独占的（见下面的“作用域标签”）。 -当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](administration/customizing-gitea.md#labels)。在创建仓库时，这些标签也将被创建。 +当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](../administration/customizing-gitea.md#labels)。在创建仓库时，这些标签也将被创建。 ## 作用域标签 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/linked-references.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/linked-references.md index 2f1b8880..3736dca5 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/linked-references.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/linked-references.md @@ -66,7 +66,7 @@ menu: ## 可操作的引用在合并请求和提交消息中 -有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](administration/config-cheat-sheet.md)。 +有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](../administration/config-cheat-sheet.md)。 示例： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/push.md b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/push.md index f9fd687c..4cc3279a 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/push.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/current/usage/push.md @@ -49,7 +49,7 @@ git push -o repo.private=false -u origin main ## 启用推送创建 -在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。 +在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](../administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。 ## 使用推送创建 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/cmd-embedded.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/cmd-embedded.md index 27ee6104..22e26d99 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/cmd-embedded.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/cmd-embedded.md @@ -17,7 +17,7 @@ menu: # 嵌入资源提取工具 -Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](administration/customizing-gitea.md)）。 +Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](../administration/customizing-gitea.md)）。 要获取嵌入资源的副本以进行编辑，可以使用 CLI 中的 `embedded` 命令，通过操作系统的 shell 执行。 @@ -71,7 +71,7 @@ gitea [--config {file}] embedded extract [--destination {dir}|--custom] [--overw `--destination` 选项用于指定提取文件的目标目录。默认为当前目录。 -`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md)。 +`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](../administration/customizing-gitea.md)。 `--overwrite` 标志允许覆盖目标目录中的任何现有文件。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/email-setup.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/email-setup.md index 877a37a2..eab4d3d8 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/email-setup.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/email-setup.md @@ -56,7 +56,7 @@ PASSWD = `password` 要发送测试邮件以验证设置，请转到 Gitea > 站点管理 > 配置 > SMTP 邮件配置。 -有关所有选项的完整列表，请查看[配置速查表](administration/config-cheat-sheet.md)。 +有关所有选项的完整列表，请查看[配置速查表](../administration/config-cheat-sheet.md)。 请注意：只有在使用 TLS 或 `HOST=localhost` 加密 SMTP 服务器通信时才支持身份验证。TLS 加密可以通过以下方式进行： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/external-renderers.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/external-renderers.md index 0b53b452..f56d6cc5 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/external-renderers.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/administration/external-renderers.md @@ -23,7 +23,7 @@ Gitea 通过外部二进制文件支持自定义文件渲染（例如 Jupyter no - 在您的 `app.ini` 文件中添加一些配置 - 重新启动 Gitea 实例 -此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md) 页面上的一些示例。 +此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](../administration/customizing-gitea.md) 页面上的一些示例。 ## 安装外部二进制文件 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/development/hacking-on-gitea.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/development/hacking-on-gitea.md index 6c3dc5b6..c737a920 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/development/hacking-on-gitea.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/development/hacking-on-gitea.md @@ -243,7 +243,7 @@ make swagger-check ### 创建新的配置选项 创建新的配置选项时，将它们添加到 `modules/setting` 的对应文件。您应该将信息添加到 `custom/conf/app.ini` -并到[配置备忘单](administration/config-cheat-sheet.md) +并到[配置备忘单](../administration/config-cheat-sheet.md) 在 `docs/content/doc/advanced/config-cheat-sheet.en-us.md` 中找到 ### 更改Logo diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/help/faq.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/help/faq.md index e1b3b6fa..2caeeee2 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/help/faq.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/help/faq.md @@ -88,7 +88,7 @@ https://github.com/loganinak/MigrateGitlabToGogs 有几个地方可能会导致显示不正确。 -1. 如果使用反向代理，请确保按照[反向代理指南](administration/reverse-proxies.md)中的正确说明进行设置。 +1. 如果使用反向代理，请确保按照[反向代理指南](../administration/reverse-proxies.md)中的正确说明进行设置。 2. 确保在`app.ini`的`server`部分中正确设置了`ROOT_URL`。 如果某些克隆选项未显示（HTTP/S或SSH），可以在`app.ini中` @@ -101,7 +101,7 @@ https://github.com/loganinak/MigrateGitlabToGogs 当反向代理限制文件上传大小时，会出现此错误。 -有关使用nginx解决此问题，请参阅[反向代理指南](administration/reverse-proxies.md)。 +有关使用nginx解决此问题，请参阅[反向代理指南](../administration/reverse-proxies.md)。 ## 自定义模板无法加载或运行错误 @@ -114,7 +114,7 @@ Gitea的自定义模板必须将其添加到正确的位置，否则Gitea将无 如果找不到，请尝试`echo $GITEA_CUSTOM`。 2. 如果仍然找不到，默认值可以被[计算](help/faq.md#where-does-gitea-store-what-file) -3. 如果仍然找不到路径，则可以参考[自定义Gitea](administration/customizing-gitea.md)页面，将模板添加到正确的位置。 +3. 如果仍然找不到路径，则可以参考[自定义Gitea](../administration/customizing-gitea.md)页面，将模板添加到正确的位置。 ## Gitea是否有"GitHub/GitLab Pages"功能？ @@ -132,7 +132,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 ## 设置日志记录 -- [官方文档](administration/logging-documentation.md) +- [官方文档](../administration/logging-documentation.md) ## 什么是Swagger？ @@ -155,7 +155,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 1. 通过设置电子邮件域名的白名单或黑名单。 2. 通过设置一些域名或者OpenID白名单（见下文）。 3. 在您的`app.ini`中将`ENABLE_CAPTCHA`设置为`true`，并正确配置`RECAPTCHA_SECRET`和 `RECAPTCHA_SITEKEY`。 -4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。 +4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](../administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。 ### 仅允许/阻止特定的电子邮件域名 @@ -181,7 +181,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 ### 启用 Fail2ban -使用 [Fail2Ban](administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。 +使用 [Fail2Ban](../administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。 ## 如何添加/使用自定义主题 @@ -334,24 +334,24 @@ error: failed to push some refs to '' ## 如何在启动 Gitea 之前创建用户 -Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](administration/command-line.md#admin)像正常情况下添加用户。 +Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](../administration/command-line.md#admin)像正常情况下添加用户。 ## 如何启用密码重置 -没有密码重置的设置。当配置了[邮件服务](administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。 +没有密码重置的设置。当配置了[邮件服务](../administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。 ## 如何更改用户的密码 - 作为管理员，您可以更改任何用户的密码（并可选择强制其在下次登录时更改密码）... - 转到您的`站点管理 -> 用户账户`页面并编辑用户。 -- 使用[管理 CLI 命令](administration/command-line.md#admin)。 +- 使用[管理 CLI 命令](../administration/command-line.md#admin)。 - 请注意，大多数命令还需要一个[全局标志](administration/command-line.md#global-options)来指向正确的配置。 + 请注意，大多数命令还需要一个[全局标志](../administration/command-line.md#global-options)来指向正确的配置。 - 作为**用户**，您可以更改密码... - 在您的账户的`设置 -> 账户`页面（此方法**需要**您知道当前密码）。 - 使用`忘记密码`链接。 - 如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](administration/email-setup.md)。 + 如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](../administration/email-setup.md)。 ## 为什么我的 Markdown 显示错误 @@ -463,6 +463,6 @@ gitea doctor recreate-table - 您还可以在`/admin/config`中检查存储库根路径。 - 确保存在要采用存储库的用户/组织。 - 作为管理员，转到`/admin/repos/unadopted`并搜索。 -- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository) 获得类似的权限。 +- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository) 获得类似的权限。 - 如果上述步骤都正确执行，您应该能够选择要采用的存储库。 - - 如果没有找到存储库，请启用[调试日志记录](administration/config-cheat-sheet.md#repository)以检查是否有特定错误。 + - 如果没有找到存储库，请启用[调试日志记录](../administration/config-cheat-sheet.md#repository-repository)以检查是否有特定错误。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/help/search.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/help/search.md deleted file mode 100644 index dc159bb7..00000000 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/help/search.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -date: "2019-11-12T16:00:00+02:00" -title: "搜索" -slug: "search" -sidebar_position: 1 -toc: false -draft: false -sitemap: - priority : 1 -layout: "search" ---- - -This file exists solely to respond to /search URL with the related `search` layout template. - -No content shown here is rendered, all content is based in the template layouts/doc/search.html - -Setting a very low sitemap priority will tell search engines this is not important content. diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/installation/from-binary.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/installation/from-binary.md index 078552f2..d84be030 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/installation/from-binary.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/installation/from-binary.md @@ -55,7 +55,7 @@ gpg --verify gitea-@version@-linux-amd64.asc gitea-@version@-linux-amd64 ## 服务器设置 -**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](administration/environment-variables.md) 初始化。 +**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](../administration/environment-variables.md) 初始化。 ### 准备环境 @@ -103,7 +103,7 @@ chmod 770 /etc/gitea - 使用 `gitea generate secret` 创建 `SECRET_KEY` 和 `INTERNAL_TOKEN` - 提供所有必要的密钥 -详情参考 [命令行文档](/zh-cn/command-line/) 中有关 `gitea generate secret` 的内容。 +详情参考 [命令行文档](../administration/command-line.md) 中有关 `gitea generate secret` 的内容。 ### 配置 Gitea 工作路径 @@ -137,7 +137,7 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini 您可以通过停止程序，替换 `/usr/local/bin/gitea` 并重启来更新到新版本。直接替换可执行程序时不要更改或使用新的文件名称，以避免数据出错。 -建议您在更新之前进行[备份](administration/backup-and-restore.md)。 +建议您在更新之前进行[备份](../administration/backup-and-restore.md)。 ### 1. 使用 systemd 重新启动 Gitea（推荐） diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/installation/from-source.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/installation/from-source.md index 938addd9..a33bb831 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/installation/from-source.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/installation/from-source.md @@ -50,7 +50,7 @@ git checkout v@version@ - `go` @minGoVersion@ 或以上版本, 详见[这里](https://golang.google.cn/doc/install) - `node` @minNodeVersion@ 或以上版本，并且安装 `npm`, 详见[这里](https://nodejs.org/zh-cn/download/) -- `make`, 详见[这里](/zh-cn/hacking-on-gitea/) +- `make`, 详见[这里](development/hacking-on-gitea.md) 各种可用的 [make 任务](https://github.com/go-gitea/gitea/blob/main/Makefile) 可以用来使编译过程更方便。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/labels.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/labels.md index e11bfca0..746bf6bb 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/labels.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/labels.md @@ -27,7 +27,7 @@ menu: 标签具有必填的名称和颜色，可选的描述，以及必须是独占的或非独占的（见下面的“作用域标签”）。 -当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](../customizing-gitea/#labels)。在创建仓库时，这些标签也将被创建。 +当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](../administration/customizing-gitea.md#labels)。在创建仓库时，这些标签也将被创建。 ## 作用域标签 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/linked-references.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/linked-references.md index 4d63d754..f49b51ff 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/linked-references.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/linked-references.md @@ -66,7 +66,7 @@ menu: ## 可操作的引用在合并请求和提交消息中 -有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](administration/config-cheat-sheet.md)。 +有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](../administration/config-cheat-sheet.md)。 示例： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/push.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/push.md index f9fd687c..4cc3279a 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/push.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.19/usage/push.md @@ -49,7 +49,7 @@ git push -o repo.private=false -u origin main ## 启用推送创建 -在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。 +在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](../administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。 ## 使用推送创建 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/cmd-embedded.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/cmd-embedded.md index 27ee6104..22e26d99 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/cmd-embedded.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/cmd-embedded.md @@ -17,7 +17,7 @@ menu: # 嵌入资源提取工具 -Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](administration/customizing-gitea.md)）。 +Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](../administration/customizing-gitea.md)）。 要获取嵌入资源的副本以进行编辑，可以使用 CLI 中的 `embedded` 命令，通过操作系统的 shell 执行。 @@ -71,7 +71,7 @@ gitea [--config {file}] embedded extract [--destination {dir}|--custom] [--overw `--destination` 选项用于指定提取文件的目标目录。默认为当前目录。 -`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md)。 +`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](../administration/customizing-gitea.md)。 `--overwrite` 标志允许覆盖目标目录中的任何现有文件。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/customizing-gitea.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/customizing-gitea.md index 2babf03d..560f8ed8 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/customizing-gitea.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/customizing-gitea.md @@ -23,13 +23,13 @@ Gitea 引用 `custom` 目录中的自定义配置文件来覆盖配置、模板 将会自动创建包括 `custom/` 在内的必要应用目录，应用本身的配置存放在 `custom/conf/app.ini` 当中。在发行版中可能会以 `/etc/gitea/` 的形式为 `custom` 设置一个符号链接，查看配置详情请移步： -- [快速备忘单](administration/config-cheat-sheet.md) +- [快速备忘单](../administration/config-cheat-sheet.md) - [完整配置清单](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini) 如果您在 binary 同目录下无法找到 `custom` 文件夹，请检查您的 `GITEA_CUSTOM` 环境变量配置， 因为它可能被配置到了其他地方（可能被一些启动脚本设置指定了目录）。 -- [环境变量清单](administration/environment-variables.md) +- [环境变量清单](../administration/environment-variables.md) **注：** 必须完全重启 Gitea 以使配置生效。 @@ -87,4 +87,4 @@ Gitea 引用 `custom` 目录中的自定义配置文件来覆盖配置、模板 ## 更改 Gitea 外观 Gitea 目前由两种内置主题，分别为默认 `gitea` 主题和深色主题 `arc-green`，您可以通过修改 -`app.ini` [ui](administration/config-cheat-sheet.md#ui-ui) 部分的 `DEFAULT_THEME` 的值来变更至一个可用的 Gitea 外观。 +`app.ini` [ui](../administration/config-cheat-sheet.md#ui-ui) 部分的 `DEFAULT_THEME` 的值来变更至一个可用的 Gitea 外观。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/email-setup.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/email-setup.md index 89a02514..eb1f6a9b 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/email-setup.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/email-setup.md @@ -55,7 +55,7 @@ PASSWD = `password` 要发送测试邮件以验证设置，请转到 Gitea > 站点管理 > 配置 > SMTP 邮件配置。 -有关所有选项的完整列表，请查看[配置速查表](administration/config-cheat-sheet.md)。 +有关所有选项的完整列表，请查看[配置速查表](../administration/config-cheat-sheet.md)。 请注意：只有在使用 TLS 或 `HOST=localhost` 加密 SMTP 服务器通信时才支持身份验证。TLS 加密可以通过以下方式进行： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/external-renderers.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/external-renderers.md index 0b53b452..f56d6cc5 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/external-renderers.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/external-renderers.md @@ -23,7 +23,7 @@ Gitea 通过外部二进制文件支持自定义文件渲染（例如 Jupyter no - 在您的 `app.ini` 文件中添加一些配置 - 重新启动 Gitea 实例 -此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md) 页面上的一些示例。 +此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](../administration/customizing-gitea.md) 页面上的一些示例。 ## 安装外部二进制文件 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/fail2ban-setup.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/fail2ban-setup.md index 457afba9..a70ed988 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/fail2ban-setup.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/fail2ban-setup.md @@ -91,4 +91,4 @@ REVERSE_PROXY_TRUSTED_PROXIES = 127.0.0.0/8,::1/128 `REVERSE_PROXY_LIMIT` 限制反向代理服务器的层数，设置为 `0` 表示不使用这些标头。 `REVERSE_PROXY_TRUSTED_PROXIES` 表示受信任的反向代理服务器网络地址， 经过该网络地址转发来的流量会经过解析 `X-Real-IP` 头部得到真实客户端地址。 -（参考 [configuration cheat sheet](administration/config-cheat-sheet.md#security-security)） +（参考 [configuration cheat sheet](../administration/config-cheat-sheet.md#security-security)） diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/https-support.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/https-support.md index add7906c..93ea93ae 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/https-support.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/https-support.md @@ -20,7 +20,7 @@ menu: 在启用HTTPS之前，确保您拥有有效的SSL/TLS证书。 建议在测试和评估情况下使用自签名证书，请运行 `gitea cert --host [HOST]` 以生成自签名证书 -如果您在服务器上使用阿帕奇（Apache）或Nginx，建议参考 [反向代理指南](administration/reverse-proxies.md)。 +如果您在服务器上使用阿帕奇（Apache）或Nginx，建议参考 [反向代理指南](../administration/reverse-proxies.md)。 要使用Gitea内置HTTPS支持，您必须编辑`app.ini`文件。 @@ -33,7 +33,7 @@ CERT_FILE = cert.pem KEY_FILE = key.pem ``` -请注意，如果您的证书由第三方证书颁发机构签名（即不是自签名的），则 cert.pem 应包含证书链。服务器证书必须是 cert.pem 中的第一个条目，后跟中介（如果有）。不必包含根证书，因为连接客户端必须已经拥有根证书才能建立信任关系。要了解有关配置值的更多信息，请查看 [配置备忘单](../config-cheat-sheet#server-server)。 +请注意，如果您的证书由第三方证书颁发机构签名（即不是自签名的），则 cert.pem 应包含证书链。服务器证书必须是 cert.pem 中的第一个条目，后跟中介（如果有）。不必包含根证书，因为连接客户端必须已经拥有根证书才能建立信任关系。要了解有关配置值的更多信息，请查看 [配置备忘单](../administration/config-cheat-sheet.md#server-server)。 对于“CERT_FILE”或“KEY_FILE”字段，当文件路径是相对路径时，文件路径相对于“GITEA_CUSTOM”环境变量。它也可以是绝对路径。 @@ -82,11 +82,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -要了解关于配置, 请访问 [配置备忘单](administration/config-cheat-sheet.md#server-server)获取更多信息 +要了解关于配置, 请访问 [配置备忘单](../administration/config-cheat-sheet.md#server-server)获取更多信息 ## 使用反向代理服务器 -按照 [reverse proxy guide](administration/reverse-proxies.md) 的规则设置你的反向代理服务器 +按照 [reverse proxy guide](../administration/reverse-proxies.md) 的规则设置你的反向代理服务器 然后，按照下面的向导启用 HTTPS： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/mail-templates.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/mail-templates.md index 6a31d65b..8b58a78c 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/mail-templates.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/mail-templates.md @@ -17,7 +17,7 @@ menu: # 邮件模板 -为了定制特定操作的电子邮件主题和内容，可以使用模板来自定义 Gitea。这些功能的模板位于 [`custom` 目录](administration/customizing-gitea.md) 下。 +为了定制特定操作的电子邮件主题和内容，可以使用模板来自定义 Gitea。这些功能的模板位于 [`custom` 目录](../administration/customizing-gitea.md) 下。 如果没有自定义的替代方案，Gitea 将使用内部模板作为默认模板。 自定义模板在 Gitea 启动时加载。对它们的更改在 Gitea 重新启动之前不会被识别。 @@ -148,7 +148,7 @@ _主题_ 和 _邮件正文_ 由 [Golang的模板引擎](https://golang.org/pkg/t 如果模板无法呈现，则只有在发送邮件时才会注意到。 如果主题模板失败，将使用默认主题，如果从 _邮件正文_ 中成功呈现了任何内容，则将使用该内容，忽略其他内容。 -如果遇到问题，请检查 [Gitea的日志](administration/logging-config.md) 以获取错误消息。 +如果遇到问题，请检查 [Gitea的日志](../administration/logging-config.md) 以获取错误消息。 ## 示例 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/repo-indexer.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/repo-indexer.md index d70a617a..5c394642 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/repo-indexer.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/administration/repo-indexer.md @@ -19,7 +19,7 @@ menu: ## 设置仓库索引器 -通过在您的 [`app.ini`](administration/config-cheat-sheet.md) 中启用此功能，Gitea 可以通过仓库的文件进行搜索： +通过在您的 [`app.ini`](../administration/config-cheat-sheet.md) 中启用此功能，Gitea 可以通过仓库的文件进行搜索： ```ini [indexer] diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/development/api-usage.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/development/api-usage.md index c7eeceeb..aeea9d94 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/development/api-usage.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/development/api-usage.md @@ -20,7 +20,7 @@ menu: ## 开启/配置 API 访问 通常情况下， `ENABLE_SWAGGER` 默认开启并且参数 `MAX_RESPONSE_ITEMS` 默认为 50。您可以从 [Config Cheat -Sheet](administration/config-cheat-sheet.md) 中获取更多配置相关信息。 +Sheet](../administration/config-cheat-sheet.md) 中获取更多配置相关信息。 ## 通过 API 认证 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/development/hacking-on-gitea.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/development/hacking-on-gitea.md index 8e32c4c2..12ce8778 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/development/hacking-on-gitea.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/development/hacking-on-gitea.md @@ -245,7 +245,7 @@ make swagger-check ### 创建新的配置选项 创建新的配置选项时，将它们添加到 `modules/setting` 的对应文件。您应该将信息添加到 `custom/conf/app.ini` -并到[配置备忘单](administration/config-cheat-sheet.md) +并到[配置备忘单](../administration/config-cheat-sheet.md) 在 `docs/content/doc/advanced/config-cheat-sheet.zh-cn.md` 中找到 ### 更改Logo diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/help/faq.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/help/faq.md index d94fbb52..e8e4cd16 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/help/faq.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/help/faq.md @@ -88,7 +88,7 @@ https://github.com/loganinak/MigrateGitlabToGogs 有几个地方可能会导致显示不正确。 -1. 如果使用反向代理，请确保按照[反向代理指南](administration/reverse-proxies.md)中的正确说明进行设置。 +1. 如果使用反向代理，请确保按照[反向代理指南](../administration/reverse-proxies.md)中的正确说明进行设置。 2. 确保在`app.ini`的`server`部分中正确设置了`ROOT_URL`。 如果某些克隆选项未显示（HTTP/S或SSH），可以在`app.ini中` @@ -101,7 +101,7 @@ https://github.com/loganinak/MigrateGitlabToGogs 当反向代理限制文件上传大小时，会出现此错误。 -有关使用nginx解决此问题，请参阅[反向代理指南](administration/reverse-proxies.md)。 +有关使用nginx解决此问题，请参阅[反向代理指南](../administration/reverse-proxies.md)。 ## 自定义模板无法加载或运行错误 @@ -114,7 +114,7 @@ Gitea的自定义模板必须将其添加到正确的位置，否则Gitea将无 如果找不到，请尝试`echo $GITEA_CUSTOM`。 2. 如果仍然找不到，默认值可以被[计算](help/faq.md#where-does-gitea-store-what-file) -3. 如果仍然找不到路径，则可以参考[自定义Gitea](administration/customizing-gitea.md)页面，将模板添加到正确的位置。 +3. 如果仍然找不到路径，则可以参考[自定义Gitea](../administration/customizing-gitea.md)页面，将模板添加到正确的位置。 ## Gitea是否有"GitHub/GitLab Pages"功能？ @@ -132,7 +132,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 ## 设置日志记录 -- [官方文档](administration/logging-config.md) +- [官方文档](../administration/logging-config.md) ## 什么是Swagger？ @@ -155,7 +155,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 1. 通过设置电子邮件域名的白名单或黑名单。 2. 通过设置一些域名或者OpenID白名单（见下文）。 3. 在您的`app.ini`中将`ENABLE_CAPTCHA`设置为`true`，并正确配置`RECAPTCHA_SECRET`和 `RECAPTCHA_SITEKEY`。 -4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。 +4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](../administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。 ### 仅允许/阻止特定的电子邮件域名 @@ -181,7 +181,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 ### 启用 Fail2ban -使用 [Fail2Ban](administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。 +使用 [Fail2Ban](../administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。 ## 如何添加/使用自定义主题 @@ -334,24 +334,24 @@ error: failed to push some refs to '' ## 如何在启动 Gitea 之前创建用户 -Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](administration/command-line.md#admin)像正常情况下添加用户。 +Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](../administration/command-line.md#admin)像正常情况下添加用户。 ## 如何启用密码重置 -没有密码重置的设置。当配置了[邮件服务](administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。 +没有密码重置的设置。当配置了[邮件服务](../administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。 ## 如何更改用户的密码 - 作为管理员，您可以更改任何用户的密码（并可选择强制其在下次登录时更改密码）... - 转到您的`站点管理 -> 用户账户`页面并编辑用户。 -- 使用[管理 CLI 命令](administration/command-line.md#admin)。 +- 使用[管理 CLI 命令](../administration/command-line.md#admin)。 - 请注意，大多数命令还需要一个[全局标志](administration/command-line.md#global-options)来指向正确的配置。 + 请注意，大多数命令还需要一个[全局标志](../administration/command-line.md#global-options)来指向正确的配置。 - 作为**用户**，您可以更改密码... - 在您的账户的`设置 -> 账户`页面（此方法**需要**您知道当前密码）。 - 使用`忘记密码`链接。 - 如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](administration/email-setup.md)。 + 如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](../administration/email-setup.md)。 ## 为什么我的 Markdown 显示错误 @@ -463,6 +463,6 @@ gitea doctor recreate-table - 您还可以在`/admin/config`中检查存储库根路径。 - 确保存在要采用存储库的用户/组织。 - 作为管理员，转到`/admin/repos/unadopted`并搜索。 -- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository) 获得类似的权限。 +- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository) 获得类似的权限。 - 如果上述步骤都正确执行，您应该能够选择要采用的存储库。 - - 如果没有找到存储库，请启用[调试日志记录](administration/config-cheat-sheet.md#repository)以检查是否有特定错误。 + - 如果没有找到存储库，请启用[调试日志记录](../administration/config-cheat-sheet.md#repository-repository)以检查是否有特定错误。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/from-binary.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/from-binary.md index a456aa28..045845d2 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/from-binary.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/from-binary.md @@ -57,7 +57,7 @@ gpg --verify gitea-@version@-linux-amd64.asc gitea-@version@-linux-amd64 ## 服务器设置 -**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](administration/environment-variables.md) 初始化。 +**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](../administration/environment-variables.md) 初始化。 ### 准备环境 @@ -117,7 +117,7 @@ chmod 770 /etc/gitea - 使用 `gitea generate secret` 创建 `SECRET_KEY` 和 `INTERNAL_TOKEN` - 提供所有必要的密钥 -详情参考 [命令行文档](administration/command-line.md) 中有关 `gitea generate secret` 的内容。 +详情参考 [命令行文档](../administration/command-line.md) 中有关 `gitea generate secret` 的内容。 ### 配置 Gitea 工作路径 @@ -151,7 +151,7 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini 您可以通过停止程序，替换 `/usr/local/bin/gitea` 并重启来更新到新版本。直接替换可执行程序时不要更改或使用新的文件名称，以避免数据出错。 -建议您在更新之前进行[备份](administration/backup-and-restore.md)。 +建议您在更新之前进行[备份](../administration/backup-and-restore.md)。 ### 1. 使用 systemd 重新启动 Gitea（推荐） diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/with-docker-rootless.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/with-docker-rootless.md index d2888cbd..2432adf5 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/with-docker-rootless.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/with-docker-rootless.md @@ -283,7 +283,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -要设置所需的 TOKEN 和 SECRET 值，可以使用 Gitea 的内置[生成使用函数](administration/command-line.md#generate). +要设置所需的 TOKEN 和 SECRET 值，可以使用 Gitea 的内置[生成使用函数](../administration/command-line.md#generate). # SSH 容器透传 @@ -312,7 +312,7 @@ sudo chmod +x /usr/local/bin/gitea-shell sudo usermod -s /usr/local/bin/gitea-shell git ``` -现在，所有的 SSH 命令都会被转发到容器，您需要在主机上设置 SSH 认证。这可以通过利用 [SSH AuthorizedKeysCommand](administration/command-line.md#keys) 来匹配 Gitea 接受的密钥。在主机的 `/etc/ssh/sshd_config` 文件中添加以下代码块： +现在，所有的 SSH 命令都会被转发到容器，您需要在主机上设置 SSH 认证。这可以通过利用 [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) 来匹配 Gitea 接受的密钥。在主机的 `/etc/ssh/sshd_config` 文件中添加以下代码块： ```bash Match User git diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/with-docker.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/with-docker.md index fcaff1c1..533c5887 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/with-docker.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/installation/with-docker.md @@ -260,7 +260,7 @@ MySQL 或 PostgreSQL 容器将需要分别创建。 ## 自定义 -[此处](administration/customizing-gitea.md)描述的定制文件应放在 `/data/gitea` 目录中。如果使用主机卷，则访问这些文件非常容易；对于命名卷，可以通过另一个容器或通过直接访问 `/var/lib/docker/volumes/gitea_gitea/_data` 来完成。安装后，配置文件将保存在 `/data/gitea/conf/app.ini` 中。 +[此处](../administration/customizing-gitea.md)描述的定制文件应放在 `/data/gitea` 目录中。如果使用主机卷，则访问这些文件非常容易；对于命名卷，可以通过另一个容器或通过直接访问 `/var/lib/docker/volumes/gitea_gitea/_data` 来完成。安装后，配置文件将保存在 `/data/gitea/conf/app.ini` 中。 ## 升级 @@ -293,7 +293,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -Gitea 将为每次新安装自动生成新的 `SECRET_KEY` 并将它们写入 `app.ini`。 如果您想手动设置 `SECRET_KEY`，您可以使用以下 docker 命令来使用 Gitea 内置的[方法](administration/command-line.md#generate)生成 `SECRET_KEY`。 安装后请妥善保管您的 `SECRET_KEY`，如若丢失则无法解密已加密的数据。 +Gitea 将为每次新安装自动生成新的 `SECRET_KEY` 并将它们写入 `app.ini`。 如果您想手动设置 `SECRET_KEY`，您可以使用以下 docker 命令来使用 Gitea 内置的[方法](../administration/command-line.md#generate)生成 `SECRET_KEY`。 安装后请妥善保管您的 `SECRET_KEY`，如若丢失则无法解密已加密的数据。 以下命令将向 `stdout` 输出一个新的 `SECRET_KEY` 和 `INTERNAL_TOKEN`，然后您可以将其放入环境变量中。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/search.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/search.md deleted file mode 100644 index 6ab5ad08..00000000 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/search.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -date: "2019-11-12T16:00:00+02:00" -title: "搜索" -slug: "search" -sidebar_position: 1 -toc: false -draft: false -aliases: - - /zh-cn/help/search -sitemap: - priority : 1 -layout: "search" ---- - -This file exists solely to respond to /search URL with the related `search` layout template. - -No content shown here is rendered, all content is based in the template layouts/doc/search.html - -Setting a very low sitemap priority will tell search engines this is not important content. diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/comparison.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/comparison.md index 88f4306f..8a82503f 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/comparison.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/comparison.md @@ -128,7 +128,7 @@ Gitea Actions默认不从GitHub下载Actions。 这意味着`uses: actions/checkout@v3`将从[gitea.com/actions/checkout](https://gitea.com/actions/checkout)下载该Action，而不是[github.com/actions/checkout](https://github.com/actions/checkout)。 正如前面提到的，这是可配置的。 -如果您希望您的运行程序默认从GitHub或您自己的Gitea实例下载动作，您可以通过设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单](administration/config-cheat-sheet.md#actions-actions)。 +如果您希望您的运行程序默认从GitHub或您自己的Gitea实例下载动作，您可以通过设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单](../../administration/config-cheat-sheet.md#actions-actions)。 ### 上下文可用性 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/faq.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/faq.md index 7bb79d02..4e14e888 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/faq.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/faq.md @@ -61,7 +61,7 @@ DEFAULT_REPO_UNITS = ...,repo.actions 注意，`https://`或`http://`前缀是必需的！ 另外，如果您希望您的Runner默认从GitHub或您自己的Gitea实例下载Actions，可以通过设置 `[actions].DEFAULT_ACTIONS_URL`进行配置。 -参见[配置速查表](administration/config-cheat-sheet.md#actions-actions)。 +参见[配置速查表](../../administration/config-cheat-sheet.md#actions-actions)。 这是与GitHub Actions的一个区别，但它应该允许用户以更灵活的方式运行Actions。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/quickstart.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/quickstart.md index 252529e0..a2478271 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/quickstart.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/actions/quickstart.md @@ -30,7 +30,7 @@ menu: ENABLED=true ``` -如果您想了解更多信息或在配置过程中遇到任何问题，请参考[配置速查表](administration/config-cheat-sheet.md#actions-actions)。 +如果您想了解更多信息或在配置过程中遇到任何问题，请参考[配置速查表](../../administration/config-cheat-sheet.md#actions-actions)。 ### 设置Runner diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/labels.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/labels.md index b9cf3930..746bf6bb 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/labels.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/labels.md @@ -27,7 +27,7 @@ menu: 标签具有必填的名称和颜色，可选的描述，以及必须是独占的或非独占的（见下面的“作用域标签”）。 -当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](administration/customizing-gitea.md#labels)。在创建仓库时，这些标签也将被创建。 +当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](../administration/customizing-gitea.md#labels)。在创建仓库时，这些标签也将被创建。 ## 作用域标签 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/linked-references.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/linked-references.md index 4d63d754..f49b51ff 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/linked-references.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/linked-references.md @@ -66,7 +66,7 @@ menu: ## 可操作的引用在合并请求和提交消息中 -有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](administration/config-cheat-sheet.md)。 +有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](../administration/config-cheat-sheet.md)。 示例： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/push.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/push.md index f9fd687c..4cc3279a 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/push.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.20/usage/push.md @@ -49,7 +49,7 @@ git push -o repo.private=false -u origin main ## 启用推送创建 -在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。 +在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](../administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。 ## 使用推送创建 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/cmd-embedded.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/cmd-embedded.md index 4570bb58..77ca53c2 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/cmd-embedded.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/cmd-embedded.md @@ -17,7 +17,7 @@ menu: # 嵌入资源提取工具 -Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](administration/customizing-gitea.md)）。 +Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](../administration/customizing-gitea.md)）。 要获取嵌入资源的副本以进行编辑，可以使用 CLI 中的 `embedded` 命令，通过操作系统的 shell 执行。 @@ -71,7 +71,7 @@ gitea [--config {file}] embedded extract [--destination {dir}|--custom] [--overw `--destination` 选项用于指定提取文件的目标目录。默认为当前目录。 -`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md)。 +`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](../administration/customizing-gitea.md)。 `--overwrite` 标志允许覆盖目标目录中的任何现有文件。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/config-cheat-sheet.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/config-cheat-sheet.md index 95f971cc..10a53225 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/config-cheat-sheet.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/config-cheat-sheet.md @@ -691,7 +691,7 @@ Gitea 创建以下非唯一队列： - `FORCE_TRUST_SERVER_CERT`: **false**：如果设置为 `true`，将完全忽略服务器证书验证错误。此选项不安全。考虑将证书添加到系统信任存储中。 - `USER`: **_empty_**：邮件用户的用户名（通常是发件人的电子邮件地址）。 - `PASSWD`: **_empty_**：邮件用户的密码。如果密码中使用了特殊字符，请使用 \`your password\` 进行引用。 - - 请注意：只有在 SMTP 服务器通信通过 TLS 加密（可以通过 `STARTTLS` 实现）或 SMTP 主机是 localhost 时，才支持身份验证。有关更多信息，请参阅 [邮件设置](administration/email-setup.md)。 + - 请注意：只有在 SMTP 服务器通信通过 TLS 加密（可以通过 `STARTTLS` 实现）或 SMTP 主机是 localhost 时，才支持身份验证。有关更多信息，请参阅 [邮件设置](../administration/email-setup.md)。 - `ENABLE_HELO`: **true**：启用 HELO 操作。 - `HELO_HOSTNAME`: **（从系统检索）**：HELO 主机名。 - `FROM`: **_empty_**：邮件的发件人地址，符合 RFC 5322。这可以是一个电子邮件地址，也可以是 "Name" \ 格式。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/customizing-gitea.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/customizing-gitea.md index 4c4efb95..abba6f42 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/customizing-gitea.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/customizing-gitea.md @@ -23,13 +23,13 @@ Gitea 引用 `custom` 目录中的自定义配置文件来覆盖配置、模板 将会自动创建包括 `custom/` 在内的必要应用目录，应用本身的配置存放在 `custom/conf/app.ini` 当中。在发行版中可能会以 `/etc/gitea/` 的形式为 `custom` 设置一个符号链接，查看配置详情请移步： -- [快速备忘单](administration/config-cheat-sheet.md) +- [快速备忘单](../administration/config-cheat-sheet.md) - [完整配置清单](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini) 如果您在 binary 同目录下无法找到 `custom` 文件夹，请检查您的 `GITEA_CUSTOM` 环境变量配置， 因为它可能被配置到了其他地方（可能被一些启动脚本设置指定了目录）。 -- [环境变量清单](administration/environment-variables.md) +- [环境变量清单](../administration/environment-variables.md) **注：** 必须完全重启 Gitea 以使配置生效。 @@ -87,4 +87,4 @@ Gitea 引用 `custom` 目录中的自定义配置文件来覆盖配置、模板 ## 更改 Gitea 外观 Gitea 目前由两种内置主题，分别为默认 `gitea` 主题和深色主题 `arc-green`，您可以通过修改 -`app.ini` [ui](administration/config-cheat-sheet.md#ui-ui) 部分的 `DEFAULT_THEME` 的值来变更至一个可用的 Gitea 外观。 +`app.ini` [ui](../administration/config-cheat-sheet.md#ui-ui) 部分的 `DEFAULT_THEME` 的值来变更至一个可用的 Gitea 外观。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/email-setup.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/email-setup.md index 7d99a5ca..4d9faa5e 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/email-setup.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/email-setup.md @@ -55,7 +55,7 @@ PASSWD = `password` 要发送测试邮件以验证设置，请转到 Gitea > 站点管理 > 配置 > SMTP 邮件配置。 -有关所有选项的完整列表，请查看[配置速查表](administration/config-cheat-sheet.md)。 +有关所有选项的完整列表，请查看[配置速查表](../administration/config-cheat-sheet.md)。 请注意：只有在使用 TLS 或 `HOST=localhost` 加密 SMTP 服务器通信时才支持身份验证。TLS 加密可以通过以下方式进行： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/external-renderers.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/external-renderers.md index fdf7315d..10138a20 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/external-renderers.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/external-renderers.md @@ -23,7 +23,7 @@ Gitea 通过外部二进制文件支持自定义文件渲染（例如 Jupyter no - 在您的 `app.ini` 文件中添加一些配置 - 重新启动 Gitea 实例 -此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md) 页面上的一些示例。 +此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](../administration/customizing-gitea.md) 页面上的一些示例。 ## 安装外部二进制文件 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/fail2ban-setup.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/fail2ban-setup.md index 457afba9..a70ed988 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/fail2ban-setup.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/fail2ban-setup.md @@ -91,4 +91,4 @@ REVERSE_PROXY_TRUSTED_PROXIES = 127.0.0.0/8,::1/128 `REVERSE_PROXY_LIMIT` 限制反向代理服务器的层数，设置为 `0` 表示不使用这些标头。 `REVERSE_PROXY_TRUSTED_PROXIES` 表示受信任的反向代理服务器网络地址， 经过该网络地址转发来的流量会经过解析 `X-Real-IP` 头部得到真实客户端地址。 -（参考 [configuration cheat sheet](administration/config-cheat-sheet.md#security-security)） +（参考 [configuration cheat sheet](../administration/config-cheat-sheet.md#security-security)） diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/https-support.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/https-support.md index 8beb06e8..815f3295 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/https-support.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/https-support.md @@ -20,7 +20,7 @@ menu: 在启用HTTPS之前，确保您拥有有效的SSL/TLS证书。 建议在测试和评估情况下使用自签名证书，请运行 `gitea cert --host [HOST]` 以生成自签名证书 -如果您在服务器上使用阿帕奇（Apache）或Nginx，建议参考 [反向代理指南](administration/reverse-proxies.md)。 +如果您在服务器上使用阿帕奇（Apache）或Nginx，建议参考 [反向代理指南](../administration/reverse-proxies.md)。 要使用Gitea内置HTTPS支持，您必须编辑`app.ini`文件。 @@ -33,7 +33,7 @@ CERT_FILE = cert.pem KEY_FILE = key.pem ``` -请注意，如果您的证书由第三方证书颁发机构签名（即不是自签名的），则 cert.pem 应包含证书链。服务器证书必须是 cert.pem 中的第一个条目，后跟中介（如果有）。不必包含根证书，因为连接客户端必须已经拥有根证书才能建立信任关系。要了解有关配置值的更多信息，请查看 [配置备忘单](administration/config-cheat-sheet#server-server)。 +请注意，如果您的证书由第三方证书颁发机构签名（即不是自签名的），则 cert.pem 应包含证书链。服务器证书必须是 cert.pem 中的第一个条目，后跟中介（如果有）。不必包含根证书，因为连接客户端必须已经拥有根证书才能建立信任关系。要了解有关配置值的更多信息，请查看 [配置备忘单](../administration/config-cheat-sheet#server-server)。 对于“CERT_FILE”或“KEY_FILE”字段，当文件路径是相对路径时，文件路径相对于“GITEA_CUSTOM”环境变量。它也可以是绝对路径。 @@ -82,11 +82,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -要了解关于配置, 请访问 [配置备忘单](administration/config-cheat-sheet.md#server-server)获取更多信息 +要了解关于配置, 请访问 [配置备忘单](../administration/config-cheat-sheet.md#server-server)获取更多信息 ## 使用反向代理服务器 -按照 [reverse proxy guide](administration/reverse-proxies.md) 的规则设置你的反向代理服务器 +按照 [reverse proxy guide](../administration/reverse-proxies.md) 的规则设置你的反向代理服务器 然后，按照下面的向导启用 HTTPS： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/mail-templates.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/mail-templates.md index 6a31d65b..8b58a78c 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/mail-templates.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/mail-templates.md @@ -17,7 +17,7 @@ menu: # 邮件模板 -为了定制特定操作的电子邮件主题和内容，可以使用模板来自定义 Gitea。这些功能的模板位于 [`custom` 目录](administration/customizing-gitea.md) 下。 +为了定制特定操作的电子邮件主题和内容，可以使用模板来自定义 Gitea。这些功能的模板位于 [`custom` 目录](../administration/customizing-gitea.md) 下。 如果没有自定义的替代方案，Gitea 将使用内部模板作为默认模板。 自定义模板在 Gitea 启动时加载。对它们的更改在 Gitea 重新启动之前不会被识别。 @@ -148,7 +148,7 @@ _主题_ 和 _邮件正文_ 由 [Golang的模板引擎](https://golang.org/pkg/t 如果模板无法呈现，则只有在发送邮件时才会注意到。 如果主题模板失败，将使用默认主题，如果从 _邮件正文_ 中成功呈现了任何内容，则将使用该内容，忽略其他内容。 -如果遇到问题，请检查 [Gitea的日志](administration/logging-config.md) 以获取错误消息。 +如果遇到问题，请检查 [Gitea的日志](../administration/logging-config.md) 以获取错误消息。 ## 示例 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/repo-indexer.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/repo-indexer.md index d70a617a..5c394642 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/repo-indexer.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/administration/repo-indexer.md @@ -19,7 +19,7 @@ menu: ## 设置仓库索引器 -通过在您的 [`app.ini`](administration/config-cheat-sheet.md) 中启用此功能，Gitea 可以通过仓库的文件进行搜索： +通过在您的 [`app.ini`](../administration/config-cheat-sheet.md) 中启用此功能，Gitea 可以通过仓库的文件进行搜索： ```ini [indexer] diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/development/api-usage.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/development/api-usage.md index 96c19972..9c237e8a 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/development/api-usage.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/development/api-usage.md @@ -19,7 +19,7 @@ menu: ## 开启/配置 API 访问 -通常情况下， `ENABLE_SWAGGER` 默认开启并且参数 `MAX_RESPONSE_ITEMS` 默认为 50。您可以从 [Config Cheat Sheet](administration/config-cheat-sheet.md) 中获取更多配置相关信息。 +通常情况下， `ENABLE_SWAGGER` 默认开启并且参数 `MAX_RESPONSE_ITEMS` 默认为 50。您可以从 [Config Cheat Sheet](../administration/config-cheat-sheet.md) 中获取更多配置相关信息。 ## 通过 API 认证 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/development/hacking-on-gitea.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/development/hacking-on-gitea.md index 2888bd83..73b68d9f 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/development/hacking-on-gitea.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/development/hacking-on-gitea.md @@ -245,7 +245,7 @@ make swagger-check ### 创建新的配置选项 创建新的配置选项时，将它们添加到 `modules/setting` 的对应文件。您应该将信息添加到 `custom/conf/app.ini` -并到[配置备忘单](administration/config-cheat-sheet.md) +并到[配置备忘单](../administration/config-cheat-sheet.md) 在 `docs/content/doc/advanced/config-cheat-sheet.zh-cn.md` 中找到 ### 更改Logo diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/help/faq.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/help/faq.md index cb8afcbc..9062aae2 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/help/faq.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/help/faq.md @@ -88,7 +88,7 @@ https://github.com/loganinak/MigrateGitlabToGogs 有几个地方可能会导致显示不正确。 -1. 如果使用反向代理，请确保按照[反向代理指南](administration/reverse-proxies.md)中的正确说明进行设置。 +1. 如果使用反向代理，请确保按照[反向代理指南](../administration/reverse-proxies.md)中的正确说明进行设置。 2. 确保在`app.ini`的`server`部分中正确设置了`ROOT_URL`。 如果某些克隆选项未显示（HTTP/S或SSH），可以在`app.ini中` @@ -101,7 +101,7 @@ https://github.com/loganinak/MigrateGitlabToGogs 当反向代理限制文件上传大小时，会出现此错误。 -有关使用nginx解决此问题，请参阅[反向代理指南](administration/reverse-proxies.md)。 +有关使用nginx解决此问题，请参阅[反向代理指南](../administration/reverse-proxies.md)。 ## 自定义模板无法加载或运行错误 @@ -114,7 +114,7 @@ Gitea的自定义模板必须将其添加到正确的位置，否则Gitea将无 如果找不到，请尝试`echo $GITEA_CUSTOM`。 2. 如果仍然找不到，默认值可以被[计算](help/faq.md#where-does-gitea-store-what-file) -3. 如果仍然找不到路径，则可以参考[自定义Gitea](administration/customizing-gitea.md)页面，将模板添加到正确的位置。 +3. 如果仍然找不到路径，则可以参考[自定义Gitea](../administration/customizing-gitea.md)页面，将模板添加到正确的位置。 ## Gitea是否有"GitHub/GitLab Pages"功能？ @@ -132,7 +132,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 ## 设置日志记录 -- [官方文档](administration/logging-config.md) +- [官方文档](../administration/logging-config.md) ## 什么是Swagger？ @@ -155,7 +155,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 1. 通过设置电子邮件域名的白名单或黑名单。 2. 通过设置一些域名或者OpenID白名单（见下文）。 3. 在您的`app.ini`中将`ENABLE_CAPTCHA`设置为`true`，并正确配置`RECAPTCHA_SECRET`和 `RECAPTCHA_SITEKEY`。 -4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。 +4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](../administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。 ### 仅允许/阻止特定的电子邮件域名 @@ -181,7 +181,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 ### 启用 Fail2ban -使用 [Fail2Ban](administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。 +使用 [Fail2Ban](../administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。 ## 如何添加/使用自定义主题 @@ -336,24 +336,24 @@ error: failed to push some refs to '' ## 如何在启动 Gitea 之前创建用户 -Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](administration/command-line.md#admin)像正常情况下添加用户。 +Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](../administration/command-line.md#admin)像正常情况下添加用户。 ## 如何启用密码重置 -没有密码重置的设置。当配置了[邮件服务](administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。 +没有密码重置的设置。当配置了[邮件服务](../administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。 ## 如何更改用户的密码 - 作为管理员，您可以更改任何用户的密码（并可选择强制其在下次登录时更改密码）... - 转到您的`站点管理 -> 用户账户`页面并编辑用户。 -- 使用[管理 CLI 命令](administration/command-line.md#admin)。 +- 使用[管理 CLI 命令](../administration/command-line.md#admin)。 - 请注意，大多数命令还需要一个[全局标志](administration/command-line.md#global-options)来指向正确的配置。 + 请注意，大多数命令还需要一个[全局标志](../administration/command-line.md#global-options)来指向正确的配置。 - 作为**用户**，您可以更改密码... - 在您的账户的`设置 -> 账户`页面（此方法**需要**您知道当前密码）。 - 使用`忘记密码`链接。 - 如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](administration/email-setup.md)。 + 如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](../administration/email-setup.md)。 ## 为什么我的 Markdown 显示错误 @@ -465,6 +465,6 @@ gitea doctor recreate-table - 您还可以在`/admin/config`中检查存储库根路径。 - 确保存在要采用存储库的用户/组织。 - 作为管理员，转到`/admin/repos/unadopted`并搜索。 -- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository) 获得类似的权限。 +- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository) 获得类似的权限。 - 如果上述步骤都正确执行，您应该能够选择要采用的存储库。 - - 如果没有找到存储库，请启用[调试日志记录](administration/config-cheat-sheet.md#repository)以检查是否有特定错误。 + - 如果没有找到存储库，请启用[调试日志记录](../administration/config-cheat-sheet.md#repository-repository)以检查是否有特定错误。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/from-binary.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/from-binary.md index 216a6be5..069f6338 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/from-binary.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/from-binary.md @@ -57,7 +57,7 @@ gpg --verify gitea-@version@-linux-amd64.asc gitea-@version@-linux-amd64 ## 服务器设置 -**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](administration/environment-variables.md) 初始化。 +**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](../administration/environment-variables.md) 初始化。 ### 准备环境 @@ -117,7 +117,7 @@ chmod 770 /etc/gitea - 使用 `gitea generate secret` 创建 `SECRET_KEY` 和 `INTERNAL_TOKEN` - 提供所有必要的密钥 -详情参考 [命令行文档](administration/command-line.md) 中有关 `gitea generate secret` 的内容。 +详情参考 [命令行文档](../administration/command-line.md) 中有关 `gitea generate secret` 的内容。 ### 配置 Gitea 工作路径 @@ -159,7 +159,7 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini 您可以通过停止程序，替换 `/usr/local/bin/gitea` 并重启来更新到新版本。直接替换可执行程序时不要更改或使用新的文件名称，以避免数据出错。 -建议您在更新之前进行[备份](administration/backup-and-restore.md)。 +建议您在更新之前进行[备份](../administration/backup-and-restore.md)。 如果您按照上述描述执行了安装步骤，二进制文件的通用名称应为 gitea。请勿更改此名称，即不要包含版本号。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/with-docker-rootless.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/with-docker-rootless.md index d2888cbd..2432adf5 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/with-docker-rootless.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/with-docker-rootless.md @@ -283,7 +283,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -要设置所需的 TOKEN 和 SECRET 值，可以使用 Gitea 的内置[生成使用函数](administration/command-line.md#generate). +要设置所需的 TOKEN 和 SECRET 值，可以使用 Gitea 的内置[生成使用函数](../administration/command-line.md#generate). # SSH 容器透传 @@ -312,7 +312,7 @@ sudo chmod +x /usr/local/bin/gitea-shell sudo usermod -s /usr/local/bin/gitea-shell git ``` -现在，所有的 SSH 命令都会被转发到容器，您需要在主机上设置 SSH 认证。这可以通过利用 [SSH AuthorizedKeysCommand](administration/command-line.md#keys) 来匹配 Gitea 接受的密钥。在主机的 `/etc/ssh/sshd_config` 文件中添加以下代码块： +现在，所有的 SSH 命令都会被转发到容器，您需要在主机上设置 SSH 认证。这可以通过利用 [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) 来匹配 Gitea 接受的密钥。在主机的 `/etc/ssh/sshd_config` 文件中添加以下代码块： ```bash Match User git diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/with-docker.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/with-docker.md index 77ac6ab2..fcbd7016 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/with-docker.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/installation/with-docker.md @@ -260,7 +260,7 @@ MySQL 或 PostgreSQL 容器将需要分别创建。 ## 自定义 -[此处](administration/customizing-gitea.md)描述的定制文件应放在 `/data/gitea` 目录中。如果使用主机卷，则访问这些文件非常容易；对于命名卷，可以通过另一个容器或通过直接访问 `/var/lib/docker/volumes/gitea_gitea/_data` 来完成。安装后，配置文件将保存在 `/data/gitea/conf/app.ini` 中。 +[此处](../administration/customizing-gitea.md)描述的定制文件应放在 `/data/gitea` 目录中。如果使用主机卷，则访问这些文件非常容易；对于命名卷，可以通过另一个容器或通过直接访问 `/var/lib/docker/volumes/gitea_gitea/_data` 来完成。安装后，配置文件将保存在 `/data/gitea/conf/app.ini` 中。 ## 升级 @@ -295,7 +295,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -Gitea 将为每次新安装自动生成新的 `SECRET_KEY` 并将它们写入 `app.ini`。 如果您想手动设置 `SECRET_KEY`，您可以使用以下 docker 命令来使用 Gitea 内置的[方法](administration/command-line.md#generate)生成 `SECRET_KEY`。 安装后请妥善保管您的 `SECRET_KEY`，如若丢失则无法解密已加密的数据。 +Gitea 将为每次新安装自动生成新的 `SECRET_KEY` 并将它们写入 `app.ini`。 如果您想手动设置 `SECRET_KEY`，您可以使用以下 docker 命令来使用 Gitea 内置的[方法](../administration/command-line.md#generate)生成 `SECRET_KEY`。 安装后请妥善保管您的 `SECRET_KEY`，如若丢失则无法解密已加密的数据。 以下命令将向 `stdout` 输出一个新的 `SECRET_KEY` 和 `INTERNAL_TOKEN`，然后您可以将其放入环境变量中。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/search.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/search.md deleted file mode 100644 index 6ab5ad08..00000000 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/search.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -date: "2019-11-12T16:00:00+02:00" -title: "搜索" -slug: "search" -sidebar_position: 1 -toc: false -draft: false -aliases: - - /zh-cn/help/search -sitemap: - priority : 1 -layout: "search" ---- - -This file exists solely to respond to /search URL with the related `search` layout template. - -No content shown here is rendered, all content is based in the template layouts/doc/search.html - -Setting a very low sitemap priority will tell search engines this is not important content. diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/act-runner.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/act-runner.md index 387a9a70..f9af5f37 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/act-runner.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/act-runner.md @@ -113,7 +113,7 @@ Runner级别决定了从哪里获取注册令牌。 注册令牌的格式是一个随机字符串 `D0gvfu2iHfUjNqCYVljVyRV14fISpJxxxxxxxxxx`。 -注册令牌也可以通过 Gitea 的 [命令行](administration/command-line.md#actions-generate-runner-token) 获得: +注册令牌也可以通过 Gitea 的 [命令行](../../administration/command-line.md#actions-generate-runner-token) 获得: ### 注册Runner diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/comparison.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/comparison.md index 9a23ef15..7c87413f 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/comparison.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/comparison.md @@ -134,7 +134,7 @@ Gitea Actions目前不支持此功能。 如果你的 Gitea 实例是部署在一个互联网限制的网络中，也可以使用绝对地址来下载 actions。你也可以将配置项修改为 `[actions].DEFAULT_ACTIONS_URL = self`。这样所有的相对路径的actions引用，将不再会从 github.com 去下载，而会从这个 Gitea 实例自己的仓库中去下载。例如： `uses: actions/checkout@v4` 将会从 `[server].ROOT_URL`/actions/checkout.git 这个地址去下载 actions。 -设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单](administration/config-cheat-sheet.md#actions-actions)。 +设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单](../../administration/config-cheat-sheet.md#actions-actions)。 ### 上下文可用性 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/faq.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/faq.md index d6e14668..a275fd89 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/faq.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/faq.md @@ -63,7 +63,7 @@ GitHub 上有成千上万个 [Actions 脚本](https://github.com/marketplace?typ 但用户理应拥有权利去灵活决定如何运行 Actions。 另外，如果您希望您的 Runner 默认从您自己的 Gitea 实例下载 Actions，可以通过设置 `[actions].DEFAULT_ACTIONS_URL`进行配置。 -参见[配置速查表](administration/config-cheat-sheet.md#actions-actions)。 +参见[配置速查表](../../administration/config-cheat-sheet.md#actions-actions)。 ## 如何限制Runner的权限？ diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/quickstart.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/quickstart.md index ffc1f07d..ff59ce32 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/quickstart.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/actions/quickstart.md @@ -30,7 +30,7 @@ menu: ENABLED=true ``` -如果您想了解更多信息或在配置过程中遇到任何问题，请参考[配置速查表](administration/config-cheat-sheet.md#actions-actions)。 +如果您想了解更多信息或在配置过程中遇到任何问题，请参考[配置速查表](../../administration/config-cheat-sheet.md#actions-actions)。 ### 设置Runner diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/labels.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/labels.md index b9cf3930..746bf6bb 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/labels.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/labels.md @@ -27,7 +27,7 @@ menu: 标签具有必填的名称和颜色，可选的描述，以及必须是独占的或非独占的（见下面的“作用域标签”）。 -当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](administration/customizing-gitea.md#labels)。在创建仓库时，这些标签也将被创建。 +当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](../administration/customizing-gitea.md#labels)。在创建仓库时，这些标签也将被创建。 ## 作用域标签 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/linked-references.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/linked-references.md index 4d63d754..f49b51ff 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/linked-references.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/linked-references.md @@ -66,7 +66,7 @@ menu: ## 可操作的引用在合并请求和提交消息中 -有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](administration/config-cheat-sheet.md)。 +有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](../administration/config-cheat-sheet.md)。 示例： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/push.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/push.md index f9fd687c..4cc3279a 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/push.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.21/usage/push.md @@ -49,7 +49,7 @@ git push -o repo.private=false -u origin main ## 启用推送创建 -在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。 +在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](../administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。 ## 使用推送创建 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22.json b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22.json new file mode 100644 index 00000000..a3739122 --- /dev/null +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22.json @@ -0,0 +1,29 @@ +{ + "sidebar.docs.category.Installation": { + "message": "安装" + }, + "sidebar.docs.category.Administration": { + "message": "管理" + }, + "sidebar.docs.category.Usage": { + "message": "使用" + }, + "sidebar.docs.category.actions": { + "message": "Actions" + }, + "sidebar.docs.category.packages": { + "message": "软件包" + }, + "sidebar.docs.category.Development": { + "message": "开发" + }, + "sidebar.docs.category.Contributing": { + "message": "贡献" + }, + "sidebar.docs.category.Help": { + "message": "帮助" + }, + "sidebar.docs.doc.What is Gitea?": { + "message": "Gitea是什么?" + } +} diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/cmd-embedded.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/cmd-embedded.md index a2df1aa2..c799911b 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/cmd-embedded.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/cmd-embedded.md @@ -17,7 +17,7 @@ menu: # 嵌入资源提取工具 -Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](administration/customizing-gitea.md)）。 +Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](../administration/customizing-gitea.md)）。 要获取嵌入资源的副本以进行编辑，可以使用 CLI 中的 `embedded` 命令，通过操作系统的 shell 执行。 @@ -71,7 +71,7 @@ gitea [--config {file}] embedded extract [--destination {dir}|--custom] [--overw `--destination` 选项用于指定提取文件的目标目录。默认为当前目录。 -`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md)。 +`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](../administration/customizing-gitea.md)。 `--overwrite` 标志允许覆盖目标目录中的任何现有文件。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/config-cheat-sheet.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/config-cheat-sheet.md index 54eced4a..e2bd6d8b 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/config-cheat-sheet.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/config-cheat-sheet.md @@ -693,7 +693,7 @@ Gitea 创建以下非唯一队列： - `FORCE_TRUST_SERVER_CERT`: **false**：如果设置为 `true`，将完全忽略服务器证书验证错误。此选项不安全。考虑将证书添加到系统信任存储中。 - `USER`: **_empty_**：邮件用户的用户名（通常是发件人的电子邮件地址）。 - `PASSWD`: **_empty_**：邮件用户的密码。如果密码中使用了特殊字符，请使用 \`your password\` 进行引用。 - - 请注意：只有在 SMTP 服务器通信通过 TLS 加密（可以通过 `STARTTLS` 实现）或 SMTP 主机是 localhost 时，才支持身份验证。有关更多信息，请参阅 [邮件设置](administration/email-setup.md)。 + - 请注意：只有在 SMTP 服务器通信通过 TLS 加密（可以通过 `STARTTLS` 实现）或 SMTP 主机是 localhost 时，才支持身份验证。有关更多信息，请参阅 [邮件设置](../administration/email-setup.md)。 - `ENABLE_HELO`: **true**：启用 HELO 操作。 - `HELO_HOSTNAME`: **（从系统检索）**：HELO 主机名。 - `FROM`: **_empty_**：邮件的发件人地址，符合 RFC 5322。这可以是一个电子邮件地址，也可以是 "Name" \ 格式。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/customizing-gitea.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/customizing-gitea.md index f41533c6..0ebc0703 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/customizing-gitea.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/customizing-gitea.md @@ -23,13 +23,13 @@ Gitea 引用 `custom` 目录中的自定义配置文件来覆盖配置、模板 将会自动创建包括 `custom/` 在内的必要应用目录，应用本身的配置存放在 `custom/conf/app.ini` 当中。在发行版中可能会以 `/etc/gitea/` 的形式为 `custom` 设置一个符号链接，查看配置详情请移步： -- [快速备忘单](administration/config-cheat-sheet.md) +- [快速备忘单](../administration/config-cheat-sheet.md) - [完整配置清单](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini) 如果您在 binary 同目录下无法找到 `custom` 文件夹，请检查您的 `GITEA_CUSTOM` 环境变量配置， 因为它可能被配置到了其他地方（可能被一些启动脚本设置指定了目录）。 -- [环境变量清单](administration/environment-variables.md) +- [环境变量清单](../administration/environment-variables.md) **注：** 必须完全重启 Gitea 以使配置生效。 @@ -88,4 +88,4 @@ Gitea 引用 `custom` 目录中的自定义配置文件来覆盖配置、模板 内置主题是“gitea-light”、“gitea-dark”和“gitea-auto”（自动适应操作系统设置）。 -默认主题可以通过 `app.ini` 的 [ui](administration/config-cheat-sheet.md#ui-ui) 部分中的 `DEFAULT_THEME` 进行更改。 +默认主题可以通过 `app.ini` 的 [ui](../administration/config-cheat-sheet.md#ui-ui) 部分中的 `DEFAULT_THEME` 进行更改。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/email-setup.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/email-setup.md index 7d99a5ca..4d9faa5e 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/email-setup.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/email-setup.md @@ -55,7 +55,7 @@ PASSWD = `password` 要发送测试邮件以验证设置，请转到 Gitea > 站点管理 > 配置 > SMTP 邮件配置。 -有关所有选项的完整列表，请查看[配置速查表](administration/config-cheat-sheet.md)。 +有关所有选项的完整列表，请查看[配置速查表](../administration/config-cheat-sheet.md)。 请注意：只有在使用 TLS 或 `HOST=localhost` 加密 SMTP 服务器通信时才支持身份验证。TLS 加密可以通过以下方式进行： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/external-renderers.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/external-renderers.md index 1e56d95a..e6c6d116 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/external-renderers.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/external-renderers.md @@ -23,7 +23,7 @@ Gitea 通过外部二进制文件支持自定义文件渲染（例如 Jupyter no - 在您的 `app.ini` 文件中添加一些配置 - 重新启动 Gitea 实例 -此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md) 页面上的一些示例。 +此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](../administration/customizing-gitea.md) 页面上的一些示例。 ## 安装外部二进制文件 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/fail2ban-setup.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/fail2ban-setup.md index 457afba9..a70ed988 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/fail2ban-setup.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/fail2ban-setup.md @@ -91,4 +91,4 @@ REVERSE_PROXY_TRUSTED_PROXIES = 127.0.0.0/8,::1/128 `REVERSE_PROXY_LIMIT` 限制反向代理服务器的层数，设置为 `0` 表示不使用这些标头。 `REVERSE_PROXY_TRUSTED_PROXIES` 表示受信任的反向代理服务器网络地址， 经过该网络地址转发来的流量会经过解析 `X-Real-IP` 头部得到真实客户端地址。 -（参考 [configuration cheat sheet](administration/config-cheat-sheet.md#security-security)） +（参考 [configuration cheat sheet](../administration/config-cheat-sheet.md#security-security)） diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/https-support.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/https-support.md index 8beb06e8..815f3295 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/https-support.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/https-support.md @@ -20,7 +20,7 @@ menu: 在启用HTTPS之前，确保您拥有有效的SSL/TLS证书。 建议在测试和评估情况下使用自签名证书，请运行 `gitea cert --host [HOST]` 以生成自签名证书 -如果您在服务器上使用阿帕奇（Apache）或Nginx，建议参考 [反向代理指南](administration/reverse-proxies.md)。 +如果您在服务器上使用阿帕奇（Apache）或Nginx，建议参考 [反向代理指南](../administration/reverse-proxies.md)。 要使用Gitea内置HTTPS支持，您必须编辑`app.ini`文件。 @@ -33,7 +33,7 @@ CERT_FILE = cert.pem KEY_FILE = key.pem ``` -请注意，如果您的证书由第三方证书颁发机构签名（即不是自签名的），则 cert.pem 应包含证书链。服务器证书必须是 cert.pem 中的第一个条目，后跟中介（如果有）。不必包含根证书，因为连接客户端必须已经拥有根证书才能建立信任关系。要了解有关配置值的更多信息，请查看 [配置备忘单](administration/config-cheat-sheet#server-server)。 +请注意，如果您的证书由第三方证书颁发机构签名（即不是自签名的），则 cert.pem 应包含证书链。服务器证书必须是 cert.pem 中的第一个条目，后跟中介（如果有）。不必包含根证书，因为连接客户端必须已经拥有根证书才能建立信任关系。要了解有关配置值的更多信息，请查看 [配置备忘单](../administration/config-cheat-sheet#server-server)。 对于“CERT_FILE”或“KEY_FILE”字段，当文件路径是相对路径时，文件路径相对于“GITEA_CUSTOM”环境变量。它也可以是绝对路径。 @@ -82,11 +82,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -要了解关于配置, 请访问 [配置备忘单](administration/config-cheat-sheet.md#server-server)获取更多信息 +要了解关于配置, 请访问 [配置备忘单](../administration/config-cheat-sheet.md#server-server)获取更多信息 ## 使用反向代理服务器 -按照 [reverse proxy guide](administration/reverse-proxies.md) 的规则设置你的反向代理服务器 +按照 [reverse proxy guide](../administration/reverse-proxies.md) 的规则设置你的反向代理服务器 然后，按照下面的向导启用 HTTPS： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/mail-templates.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/mail-templates.md index 3c7c2a93..25da3105 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/mail-templates.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/mail-templates.md @@ -17,7 +17,7 @@ menu: # 邮件模板 -为了定制特定操作的电子邮件主题和内容，可以使用模板来自定义 Gitea。这些功能的模板位于 [`custom` 目录](administration/customizing-gitea.md) 下。 +为了定制特定操作的电子邮件主题和内容，可以使用模板来自定义 Gitea。这些功能的模板位于 [`custom` 目录](../administration/customizing-gitea.md) 下。 如果没有自定义的替代方案，Gitea 将使用内部模板作为默认模板。 自定义模板在 Gitea 启动时加载。对它们的更改在 Gitea 重新启动之前不会被识别。 @@ -148,7 +148,7 @@ _主题_ 和 _邮件正文_ 由 [Golang的模板引擎](https://go.dev/pkg/text/ 如果模板无法呈现，则只有在发送邮件时才会注意到。 如果主题模板失败，将使用默认主题，如果从 _邮件正文_ 中成功呈现了任何内容，则将使用该内容，忽略其他内容。 -如果遇到问题，请检查 [Gitea的日志](administration/logging-config.md) 以获取错误消息。 +如果遇到问题，请检查 [Gitea的日志](../administration/logging-config.md) 以获取错误消息。 ## 示例 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/repo-indexer.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/repo-indexer.md index d70a617a..5c394642 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/repo-indexer.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/administration/repo-indexer.md @@ -19,7 +19,7 @@ menu: ## 设置仓库索引器 -通过在您的 [`app.ini`](administration/config-cheat-sheet.md) 中启用此功能，Gitea 可以通过仓库的文件进行搜索： +通过在您的 [`app.ini`](../administration/config-cheat-sheet.md) 中启用此功能，Gitea 可以通过仓库的文件进行搜索： ```ini [indexer] diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/development/api-usage.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/development/api-usage.md index d7aca16f..6428660b 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/development/api-usage.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/development/api-usage.md @@ -19,7 +19,7 @@ menu: ## 开启/配置 API 访问 -通常情况下， `ENABLE_SWAGGER` 默认开启并且参数 `MAX_RESPONSE_ITEMS` 默认为 50。您可以从 [Config Cheat Sheet](administration/config-cheat-sheet.md) 中获取更多配置相关信息。 +通常情况下， `ENABLE_SWAGGER` 默认开启并且参数 `MAX_RESPONSE_ITEMS` 默认为 50。您可以从 [Config Cheat Sheet](../administration/config-cheat-sheet.md) 中获取更多配置相关信息。 ## 通过 API 认证 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/development/hacking-on-gitea.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/development/hacking-on-gitea.md index 7dfea305..1cae90c3 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/development/hacking-on-gitea.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/development/hacking-on-gitea.md @@ -245,7 +245,7 @@ make swagger-check ### 创建新的配置选项 创建新的配置选项时，将它们添加到 `modules/setting` 的对应文件。您应该将信息添加到 `custom/conf/app.ini` -并到[配置备忘单](administration/config-cheat-sheet.md) +并到[配置备忘单](../administration/config-cheat-sheet.md) 在 `docs/content/doc/advanced/config-cheat-sheet.zh-cn.md` 中找到 ### 更改Logo diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/help/faq.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/help/faq.md index d24dfe24..44d01e44 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/help/faq.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/help/faq.md @@ -87,7 +87,7 @@ https://github.com/loganinak/MigrateGitlabToGogs 有几个地方可能会导致显示不正确。 -1. 如果使用反向代理，请确保按照[反向代理指南](administration/reverse-proxies.md)中的正确说明进行设置。 +1. 如果使用反向代理，请确保按照[反向代理指南](../administration/reverse-proxies.md)中的正确说明进行设置。 2. 确保在`app.ini`的`server`部分中正确设置了`ROOT_URL`。 如果某些克隆选项未显示（HTTP/S或SSH），可以在`app.ini中` @@ -100,7 +100,7 @@ https://github.com/loganinak/MigrateGitlabToGogs 当反向代理限制文件上传大小时，会出现此错误。 -有关使用nginx解决此问题，请参阅[反向代理指南](administration/reverse-proxies.md)。 +有关使用nginx解决此问题，请参阅[反向代理指南](../administration/reverse-proxies.md)。 ## 自定义模板无法加载或运行错误 @@ -113,7 +113,7 @@ Gitea的自定义模板必须将其添加到正确的位置，否则Gitea将无 如果找不到，请尝试`echo $GITEA_CUSTOM`。 2. 如果仍然找不到，默认值可以被[计算](help/faq.md#where-does-gitea-store-what-file) -3. 如果仍然找不到路径，则可以参考[自定义Gitea](administration/customizing-gitea.md)页面，将模板添加到正确的位置。 +3. 如果仍然找不到路径，则可以参考[自定义Gitea](../administration/customizing-gitea.md)页面，将模板添加到正确的位置。 ## Gitea是否有"GitHub/GitLab Pages"功能？ @@ -131,7 +131,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 ## 设置日志记录 -- [官方文档](administration/logging-config.md) +- [官方文档](../administration/logging-config.md) ## 什么是Swagger？ @@ -154,7 +154,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 1. 通过设置电子邮件域名的白名单或黑名单。 2. 通过设置一些域名或者OpenID白名单（见下文）。 3. 在您的`app.ini`中将`ENABLE_CAPTCHA`设置为`true`，并正确配置`RECAPTCHA_SECRET`和 `RECAPTCHA_SITEKEY`。 -4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。 +4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](../administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。 ### 仅允许/阻止特定的电子邮件域名 @@ -180,7 +180,7 @@ Gitea不提供内置的Pages服务器。您需要一个专用的域名来提供 ### 启用 Fail2ban -使用 [Fail2Ban](administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。 +使用 [Fail2Ban](../administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。 ## SSHD vs 内建SSH @@ -324,24 +324,24 @@ error: failed to push some refs to '' ## 如何在启动 Gitea 之前创建用户 -Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](administration/command-line.md#admin)像正常情况下添加用户。 +Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](../administration/command-line.md#admin)像正常情况下添加用户。 ## 如何启用密码重置 -没有密码重置的设置。当配置了[邮件服务](administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。 +没有密码重置的设置。当配置了[邮件服务](../administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。 ## 如何更改用户的密码 - 作为管理员，您可以更改任何用户的密码（并可选择强制其在下次登录时更改密码）... - 转到您的`站点管理 -> 用户账户`页面并编辑用户。 -- 使用[管理 CLI 命令](administration/command-line.md#admin)。 +- 使用[管理 CLI 命令](../administration/command-line.md#admin)。 - 请注意，大多数命令还需要一个[全局标志](administration/command-line.md#global-options)来指向正确的配置。 + 请注意，大多数命令还需要一个[全局标志](../administration/command-line.md#global-options)来指向正确的配置。 - 作为**用户**，您可以更改密码... - 在您的账户的`设置 -> 账户`页面（此方法**需要**您知道当前密码）。 - 使用`忘记密码`链接。 - 如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](administration/email-setup.md)。 + 如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](../administration/email-setup.md)。 ## 为什么我的 Markdown 显示错误 @@ -433,6 +433,6 @@ gitea doctor recreate-table - 您还可以在`/admin/config`中检查存储库根路径。 - 确保存在要采用存储库的用户/组织。 - 作为管理员，转到`/admin/repos/unadopted`并搜索。 -- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository) 获得类似的权限。 +- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository) 获得类似的权限。 - 如果上述步骤都正确执行，您应该能够选择要采用的存储库。 - - 如果没有找到存储库，请启用[调试日志记录](administration/config-cheat-sheet.md#repository)以检查是否有特定错误。 + - 如果没有找到存储库，请启用[调试日志记录](../administration/config-cheat-sheet.md#repository-repository)以检查是否有特定错误。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/from-binary.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/from-binary.md index 216a6be5..069f6338 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/from-binary.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/from-binary.md @@ -57,7 +57,7 @@ gpg --verify gitea-@version@-linux-amd64.asc gitea-@version@-linux-amd64 ## 服务器设置 -**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](administration/environment-variables.md) 初始化。 +**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](../administration/environment-variables.md) 初始化。 ### 准备环境 @@ -117,7 +117,7 @@ chmod 770 /etc/gitea - 使用 `gitea generate secret` 创建 `SECRET_KEY` 和 `INTERNAL_TOKEN` - 提供所有必要的密钥 -详情参考 [命令行文档](administration/command-line.md) 中有关 `gitea generate secret` 的内容。 +详情参考 [命令行文档](../administration/command-line.md) 中有关 `gitea generate secret` 的内容。 ### 配置 Gitea 工作路径 @@ -159,7 +159,7 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini 您可以通过停止程序，替换 `/usr/local/bin/gitea` 并重启来更新到新版本。直接替换可执行程序时不要更改或使用新的文件名称，以避免数据出错。 -建议您在更新之前进行[备份](administration/backup-and-restore.md)。 +建议您在更新之前进行[备份](../administration/backup-and-restore.md)。 如果您按照上述描述执行了安装步骤，二进制文件的通用名称应为 gitea。请勿更改此名称，即不要包含版本号。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/with-docker-rootless.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/with-docker-rootless.md index d2888cbd..2432adf5 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/with-docker-rootless.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/with-docker-rootless.md @@ -283,7 +283,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -要设置所需的 TOKEN 和 SECRET 值，可以使用 Gitea 的内置[生成使用函数](administration/command-line.md#generate). +要设置所需的 TOKEN 和 SECRET 值，可以使用 Gitea 的内置[生成使用函数](../administration/command-line.md#generate). # SSH 容器透传 @@ -312,7 +312,7 @@ sudo chmod +x /usr/local/bin/gitea-shell sudo usermod -s /usr/local/bin/gitea-shell git ``` -现在，所有的 SSH 命令都会被转发到容器，您需要在主机上设置 SSH 认证。这可以通过利用 [SSH AuthorizedKeysCommand](administration/command-line.md#keys) 来匹配 Gitea 接受的密钥。在主机的 `/etc/ssh/sshd_config` 文件中添加以下代码块： +现在，所有的 SSH 命令都会被转发到容器，您需要在主机上设置 SSH 认证。这可以通过利用 [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) 来匹配 Gitea 接受的密钥。在主机的 `/etc/ssh/sshd_config` 文件中添加以下代码块： ```bash Match User git diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/with-docker.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/with-docker.md index 77ac6ab2..fcbd7016 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/with-docker.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/installation/with-docker.md @@ -260,7 +260,7 @@ MySQL 或 PostgreSQL 容器将需要分别创建。 ## 自定义 -[此处](administration/customizing-gitea.md)描述的定制文件应放在 `/data/gitea` 目录中。如果使用主机卷，则访问这些文件非常容易；对于命名卷，可以通过另一个容器或通过直接访问 `/var/lib/docker/volumes/gitea_gitea/_data` 来完成。安装后，配置文件将保存在 `/data/gitea/conf/app.ini` 中。 +[此处](../administration/customizing-gitea.md)描述的定制文件应放在 `/data/gitea` 目录中。如果使用主机卷，则访问这些文件非常容易；对于命名卷，可以通过另一个容器或通过直接访问 `/var/lib/docker/volumes/gitea_gitea/_data` 来完成。安装后，配置文件将保存在 `/data/gitea/conf/app.ini` 中。 ## 升级 @@ -295,7 +295,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -Gitea 将为每次新安装自动生成新的 `SECRET_KEY` 并将它们写入 `app.ini`。 如果您想手动设置 `SECRET_KEY`，您可以使用以下 docker 命令来使用 Gitea 内置的[方法](administration/command-line.md#generate)生成 `SECRET_KEY`。 安装后请妥善保管您的 `SECRET_KEY`，如若丢失则无法解密已加密的数据。 +Gitea 将为每次新安装自动生成新的 `SECRET_KEY` 并将它们写入 `app.ini`。 如果您想手动设置 `SECRET_KEY`，您可以使用以下 docker 命令来使用 Gitea 内置的[方法](../administration/command-line.md#generate)生成 `SECRET_KEY`。 安装后请妥善保管您的 `SECRET_KEY`，如若丢失则无法解密已加密的数据。 以下命令将向 `stdout` 输出一个新的 `SECRET_KEY` 和 `INTERNAL_TOKEN`，然后您可以将其放入环境变量中。 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/search.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/search.md deleted file mode 100644 index 6ab5ad08..00000000 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/search.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -date: "2019-11-12T16:00:00+02:00" -title: "搜索" -slug: "search" -sidebar_position: 1 -toc: false -draft: false -aliases: - - /zh-cn/help/search -sitemap: - priority : 1 -layout: "search" ---- - -This file exists solely to respond to /search URL with the related `search` layout template. - -No content shown here is rendered, all content is based in the template layouts/doc/search.html - -Setting a very low sitemap priority will tell search engines this is not important content. diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/act-runner.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/act-runner.md index e5ebff97..4541a1b1 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/act-runner.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/act-runner.md @@ -113,7 +113,7 @@ Runner级别决定了从哪里获取注册令牌。 注册令牌的格式是一个随机字符串 `D0gvfu2iHfUjNqCYVljVyRV14fISpJxxxxxxxxxx`。 -注册令牌也可以通过 Gitea 的 [命令行](administration/command-line.md#actions-generate-runner-token) 获得: +注册令牌也可以通过 Gitea 的 [命令行](../../administration/command-line.md#actions-generate-runner-token) 获得: ### 注册Runner diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/comparison.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/comparison.md index 79450e8e..fdb96ceb 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/comparison.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/comparison.md @@ -132,7 +132,7 @@ Gitea Actions目前不支持此功能。 如果你的 Gitea 实例是部署在一个互联网限制的网络中，也可以使用绝对地址来下载 actions。你也可以将配置项修改为 `[actions].DEFAULT_ACTIONS_URL = self`。这样所有的相对路径的actions引用，将不再会从 github.com 去下载，而会从这个 Gitea 实例自己的仓库中去下载。例如： `uses: actions/checkout@v4` 将会从 `[server].ROOT_URL`/actions/checkout.git 这个地址去下载 actions。 -设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单](administration/config-cheat-sheet.md#actions-actions)。 +设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单](../../administration/config-cheat-sheet.md#actions-actions)。 ### 上下文可用性 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/faq.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/faq.md index 48fc3272..112fe51b 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/faq.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/faq.md @@ -63,7 +63,7 @@ GitHub 上有成千上万个 [Actions 脚本](https://github.com/marketplace?typ 但用户理应拥有权利去灵活决定如何运行 Actions。 另外，如果您希望您的 Runner 默认从您自己的 Gitea 实例下载 Actions，可以通过设置 `[actions].DEFAULT_ACTIONS_URL`进行配置。 -参见[配置速查表](administration/config-cheat-sheet.md#actions-actions)。 +参见[配置速查表](../../administration/config-cheat-sheet.md#actions-actions)。 ## 如何限制Runner的权限？ diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/quickstart.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/quickstart.md index 8fccc6c9..e94672cd 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/quickstart.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/actions/quickstart.md @@ -30,7 +30,7 @@ menu: ENABLED=true ``` -如果您想了解更多信息或在配置过程中遇到任何问题，请参考[配置速查表](administration/config-cheat-sheet.md#actions-actions)。 +如果您想了解更多信息或在配置过程中遇到任何问题，请参考[配置速查表](../../administration/config-cheat-sheet.md#actions-actions)。 ### 设置Runner diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/labels.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/labels.md index b9cf3930..746bf6bb 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/labels.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/labels.md @@ -27,7 +27,7 @@ menu: 标签具有必填的名称和颜色，可选的描述，以及必须是独占的或非独占的（见下面的“作用域标签”）。 -当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](administration/customizing-gitea.md#labels)。在创建仓库时，这些标签也将被创建。 +当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](../administration/customizing-gitea.md#labels)。在创建仓库时，这些标签也将被创建。 ## 作用域标签 diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/linked-references.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/linked-references.md index 2f1b8880..3736dca5 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/linked-references.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/linked-references.md @@ -66,7 +66,7 @@ menu: ## 可操作的引用在合并请求和提交消息中 -有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](administration/config-cheat-sheet.md)。 +有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](../administration/config-cheat-sheet.md)。 示例： diff --git a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/push.md b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/push.md index f9fd687c..4cc3279a 100644 --- a/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/push.md +++ b/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.22/usage/push.md @@ -49,7 +49,7 @@ git push -o repo.private=false -u origin main ## 启用推送创建 -在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。 +在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](../administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。 ## 使用推送创建 diff --git a/versioned_docs/version-1.19/administration/cmd-embedded.md b/versioned_docs/version-1.19/administration/cmd-embedded.md index 69aa786a..fa2c1026 100644 --- a/versioned_docs/version-1.19/administration/cmd-embedded.md +++ b/versioned_docs/version-1.19/administration/cmd-embedded.md @@ -17,7 +17,7 @@ menu: Gitea's executable contains all the resources required to run: templates, images, style-sheets and translations. Any of them can be overridden by placing a replacement in a matching path -inside the `custom` directory (see [Customizing Gitea](administration/customizing-gitea.md)). +inside the `custom` directory (see [Customizing Gitea](../administration/customizing-gitea.md)). To obtain a copy of the embedded resources ready for editing, the `embedded` command from the CLI can be used from the OS shell interface. @@ -83,7 +83,7 @@ The default is the current directory. The `--custom` flag tells Gitea to extract the files directly into the `custom` directory. For this to work, the command needs to know the location of the `app.ini` configuration file (`--config`) and, depending of the configuration, be ran from the directory where -Gitea normally starts. See [Customizing Gitea](administration/customizing-gitea.md) for details. +Gitea normally starts. See [Customizing Gitea](../administration/customizing-gitea.md) for details. The `--overwrite` flag allows any existing files in the destination directory to be overwritten. diff --git a/versioned_docs/version-1.19/administration/config-cheat-sheet.md b/versioned_docs/version-1.19/administration/config-cheat-sheet.md index 3afeb4e8..a8c45e00 100644 --- a/versioned_docs/version-1.19/administration/config-cheat-sheet.md +++ b/versioned_docs/version-1.19/administration/config-cheat-sheet.md @@ -772,7 +772,7 @@ and - `FORCE_TRUST_SERVER_CERT`: **false**: If set to `true`, completely ignores server certificate validation errors. This option is unsafe. Consider adding the certificate to the system trust store instead. - `USER`: **_empty_**: Username of mailing user (usually the sender's e-mail address). - `PASSWD`: **_empty_**: Password of mailing user. Use \`your password\` for quoting if you use special characters in the password. - - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](administration/email-setup.md) for more information. + - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](../administration/email-setup.md) for more information. - `ENABLE_HELO`: **true**: Enable HELO operation. - `HELO_HOSTNAME`: **(retrieved from system)**: HELO hostname. - `FROM`: **_empty_**: Mail from address, RFC 5322. This can be just an email address, or the "Name" \ format. diff --git a/versioned_docs/version-1.19/administration/customizing-gitea.md b/versioned_docs/version-1.19/administration/customizing-gitea.md index b1c1ef9c..e14a137b 100644 --- a/versioned_docs/version-1.19/administration/customizing-gitea.md +++ b/versioned_docs/version-1.19/administration/customizing-gitea.md @@ -82,7 +82,7 @@ directory at the top of this document). Every single page of Gitea can be changed. Dynamic content is generated using [go templates](https://golang.org/pkg/html/template/), which can be modified by placing replacements below the `$GITEA_CUSTOM/templates` directory. -To obtain any embedded file (including templates), the [`gitea embedded` tool](administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using). +To obtain any embedded file (including templates), the [`gitea embedded` tool](../administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using). Be aware that any statement contained inside `{{` and `}}` are Gitea's template syntax and shouldn't be touched without fully understanding these components. diff --git a/versioned_docs/version-1.19/administration/email-setup.md b/versioned_docs/version-1.19/administration/email-setup.md index 2bcbe152..86e41bb0 100644 --- a/versioned_docs/version-1.19/administration/email-setup.md +++ b/versioned_docs/version-1.19/administration/email-setup.md @@ -54,7 +54,7 @@ Restart Gitea for the configuration changes to take effect. To send a test email to validate the settings, go to Gitea > Site Administration > Configuration > SMTP Mailer Configuration. -For the full list of options check the [Config Cheat Sheet](administration/config-cheat-sheet.md) +For the full list of options check the [Config Cheat Sheet](../administration/config-cheat-sheet.md) Please note: authentication is only supported when the SMTP server communication is encrypted with TLS or `HOST=localhost`. TLS encryption can be through: diff --git a/versioned_docs/version-1.19/administration/external-renderers.md b/versioned_docs/version-1.19/administration/external-renderers.md index 004e68c6..585e04c2 100644 --- a/versioned_docs/version-1.19/administration/external-renderers.md +++ b/versioned_docs/version-1.19/administration/external-renderers.md @@ -22,7 +22,7 @@ it is just a matter of: - add some configuration to your `app.ini` file - restart your Gitea instance -This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](administration/customizing-gitea.md) page. +This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](../administration/customizing-gitea.md) page. ## Installing external binaries diff --git a/versioned_docs/version-1.19/administration/https-support.md b/versioned_docs/version-1.19/administration/https-support.md index 07f3565a..cb460a99 100644 --- a/versioned_docs/version-1.19/administration/https-support.md +++ b/versioned_docs/version-1.19/administration/https-support.md @@ -20,7 +20,7 @@ menu: Before you enable HTTPS, make sure that you have valid SSL/TLS certificates. You could use self-generated certificates for evaluation and testing. Please run `gitea cert --host [HOST]` to generate a self signed certificate. -If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](administration/reverse-proxies.md). +If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](../administration/reverse-proxies.md). To use Gitea's built-in HTTPS support, you must change your `app.ini` file: @@ -34,7 +34,7 @@ KEY_FILE = key.pem ``` Note that if your certificate is signed by a third party certificate authority (i.e. not self-signed), then cert.pem should contain the certificate chain. The server certificate must be the first entry in cert.pem, followed by the intermediaries in order (if any). The root certificate does not have to be included because the connecting client must already have it in order to estalbish the trust relationship. -To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](../administration/config-cheat-sheet.md#server-server). For the `CERT_FILE` or `KEY_FILE` field, the file path is relative to the `GITEA_CUSTOM` environment variable when it is a relative path. It can be an absolute path as well. @@ -83,11 +83,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](../administration/config-cheat-sheet.md#server-server). ## Using a reverse proxy -Setup up your reverse proxy as shown in the [reverse proxy guide](administration/reverse-proxies.md). +Setup up your reverse proxy as shown in the [reverse proxy guide](../administration/reverse-proxies.md). After that, enable HTTPS by following one of these guides: diff --git a/versioned_docs/version-1.19/administration/search-engines-indexation.md b/versioned_docs/version-1.19/administration/search-engines-indexation.md index 232c80ad..0abc3515 100644 --- a/versioned_docs/version-1.19/administration/search-engines-indexation.md +++ b/versioned_docs/version-1.19/administration/search-engines-indexation.md @@ -21,7 +21,7 @@ If you don't want your repository to be visible for search engines read further. ## Block search engines indexation using robots.txt To make Gitea serve a custom `robots.txt` (default: empty 404) for top level installations, -create a file called `robots.txt` in the [`custom` folder or `CustomPath`](administration/customizing-gitea.md) +create a file called `robots.txt` in the [`custom` folder or `CustomPath`](../administration/customizing-gitea.md) Examples on how to configure the `robots.txt` can be found at [https://moz.com/learn/seo/robotstxt](https://moz.com/learn/seo/robotstxt). diff --git a/versioned_docs/version-1.19/development/hacking-on-gitea.md b/versioned_docs/version-1.19/development/hacking-on-gitea.md index 29653e42..5ad40169 100644 --- a/versioned_docs/version-1.19/development/hacking-on-gitea.md +++ b/versioned_docs/version-1.19/development/hacking-on-gitea.md @@ -266,7 +266,7 @@ Please note you should use the Swagger 2.0 documentation, not the OpenAPI 3 docu When creating new configuration options, it is not enough to add them to the `modules/setting` files. You should add information to `custom/conf/app.ini` and to the -[configuration cheat sheet](administration/config-cheat-sheet.md) +[configuration cheat sheet](../administration/config-cheat-sheet.md) found in `docs/content/doc/administer/config-cheat-sheet.en-us.md` ### Changing the logo diff --git a/versioned_docs/version-1.19/help/faq.md b/versioned_docs/version-1.19/help/faq.md index 100acf7e..b31748d9 100644 --- a/versioned_docs/version-1.19/help/faq.md +++ b/versioned_docs/version-1.19/help/faq.md @@ -88,7 +88,7 @@ https://github.com/loganinak/MigrateGitlabToGogs There are a few places that could make this show incorrectly. -1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](administration/reverse-proxies.md) +1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](../administration/reverse-proxies.md) 2. Make sure you have correctly set `ROOT_URL` in the `server` section of your `app.ini` If certain clone options aren't showing up (HTTP/S or SSH), the following options can be checked in your `app.ini` @@ -101,7 +101,7 @@ If certain clone options aren't showing up (HTTP/S or SSH), the following option This error occurs when the reverse proxy limits the file upload size. -See the [reverse proxy guide](administration/reverse-proxies.md) for a solution with nginx. +See the [reverse proxy guide](../administration/reverse-proxies.md) for a solution with nginx. ## Custom Templates not loading or working incorrectly @@ -114,7 +114,7 @@ The correct path for the template(s) will be relative to the `CustomPath` If that doesn't exist, you can try `echo $GITEA_CUSTOM` 2. If you are still unable to find a path, the default can be [calculated above](#where-does-gitea-store-what-file) -3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](administration/customizing-gitea.md) page to add your template to the correct location. +3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](../administration/customizing-gitea.md) page to add your template to the correct location. ## Does Gitea have a "GitHub/GitLab pages" feature? @@ -132,7 +132,7 @@ A "login prohibited" user is a user that is not allowed to log in to Gitea anymo ## Setting up logging -- [Official Docs](administration/logging-documentation.md) +- [Official Docs](../administration/logging-documentation.md) ## What is Swagger? @@ -155,7 +155,7 @@ There are multiple things you can combine to prevent spammers. 1. By whitelisting or blocklisting certain email domains 2. By only whitelisting certain domains with OpenID (see below) 3. Setting `ENABLE_CAPTCHA` to `true` in your `app.ini` and properly configuring `RECAPTCHA_SECRET` and `RECAPTCHA_SITEKEY` -4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI +4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](../administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI ### Only allow/block certain email domains @@ -183,7 +183,7 @@ At some point, a customer or third party needs access to a specific repo and onl ### Enable Fail2ban -Use [Fail2Ban](administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns +Use [Fail2Ban](../administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns ## How to add/use custom themes @@ -336,24 +336,24 @@ You may want to set this value to `60m` or `120m`. ## How can I create users before starting Gitea -Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](administration/command-line.md#admin) to add users like normal. +Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](../administration/command-line.md#admin) to add users like normal. ## How can I enable password reset -There is no setting for password resets. It is enabled when a [mail service](administration/email-setup.md) is configured, and disabled otherwise. +There is no setting for password resets. It is enabled when a [mail service](../administration/email-setup.md) is configured, and disabled otherwise. ## How can a user's password be changed - As an **admin**, you can change any user's password (and optionally force them to change it on next login)... - By navigating to your `Site Administration -> User Accounts` page and editing a user. - - By using the [admin CLI commands](administration/command-line.md#admin). + - By using the [admin CLI commands](../administration/command-line.md#admin). - Keep in mind most commands will also need a [global flag](administration/command-line.md#global-options) to point the CLI at the correct configuration. + Keep in mind most commands will also need a [global flag](../administration/command-line.md#global-options) to point the CLI at the correct configuration. - As a **user** you can change it... - In your account `Settings -> Account` page (this method **requires** you to know your current password). - By using the `Forgot Password` link. - If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](administration/email-setup.md). + If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](../administration/email-setup.md). ## Why is my markdown broken @@ -425,13 +425,13 @@ You should only set this option once you have completely configured everything. Sometimes when there are migrations the old columns and default values may be left unchanged in the database schema. This may lead to warning such as: -``` +```log 2020/08/02 11:32:29 ...rm/session_schema.go:360:Sync2() [W] Table user Column keep_activity_private db default is , struct default is 0 ``` These can safely be ignored, but you are able to stop these warnings by getting Gitea to recreate these tables using: -``` +```bash gitea doctor recreate-table user ``` @@ -440,13 +440,13 @@ with the defaults set appropriately. You can ask Gitea to recreate multiple tables using: -``` +```bash gitea doctor recreate-table table1 table2 ... ``` And if you would like Gitea to recreate all tables simply call: -``` +```bash gitea doctor recreate-table ``` @@ -465,6 +465,6 @@ If you are using Cloudflare, turn off the auto-minify option in the dashboard. - You can also check `/admin/config` for the repository root path. - Ensure that the user/org exists that you want to adopt repositories for. - As an admin, go to `/admin/repos/unadopted` and search. - - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository). + - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository). - If the above steps are done correctly, you should be able to select repositories to adopt. - - If no repositories are found, enable [debug logging](administration/config-cheat-sheet.md#repository) to check for any specific errors. + - If no repositories are found, enable [debug logging](../administration/config-cheat-sheet.md#repository-repository) to check for any specific errors. diff --git a/versioned_docs/version-1.19/help/search.md b/versioned_docs/version-1.19/help/search.md deleted file mode 100644 index e26aaef5..00000000 --- a/versioned_docs/version-1.19/help/search.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -date: "2019-11-12T16:00:00+02:00" -title: "Search" -slug: "search" -sidebar_position: 1 -toc: false -draft: false -sitemap: - priority : 1 -layout: "search" ---- - -This file exists solely to respond to /search URL with the related `search` layout template. - -No content shown here is rendered, all content is based in the template layouts/doc/search.html - -Setting a very low sitemap priority will tell search engines this is not important content. diff --git a/versioned_docs/version-1.19/installation/from-binary.md b/versioned_docs/version-1.19/installation/from-binary.md index fedb11e5..63263b06 100644 --- a/versioned_docs/version-1.19/installation/from-binary.md +++ b/versioned_docs/version-1.19/installation/from-binary.md @@ -61,7 +61,7 @@ despite warnings like `This key is not certified with a trusted signature!`. ## Recommended server configuration :::note -Many of the following directories can be configured using [Environment Variables](administration/environment-variables.md) as well! +Many of the following directories can be configured using [Environment Variables](../administration/environment-variables.md) as well! Of note, configuring `GITEA_WORK_DIR` will tell Gitea where to base its working directory, as well as ease installation. ::: @@ -113,7 +113,7 @@ If you don't want the web installer to be able to write to the config file, it i * Ensure that the `SECRET_KEY` and `INTERNAL_TOKEN` values are set. (You may want to use the `gitea generate secret` to generate these secret keys.) * Ensure that any other secret keys you need are set. -See the [command line documentation](administration/command-line.md) for information on using `gitea generate secret`. +See the [command line documentation](../administration/command-line.md) for information on using `gitea generate secret`. ### Configure Gitea's working directory @@ -160,7 +160,7 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini You can update to a new version of Gitea by stopping Gitea, replacing the binary at `/usr/local/bin/gitea` and restarting the instance. The binary file name should not be changed during the update to avoid problems in existing repositories. -It is recommended that you make a [backup](administration/backup-and-restore.md) before updating your installation. +It is recommended that you make a [backup](../administration/backup-and-restore.md) before updating your installation. If you have carried out the installation steps as described above, the binary should have the generic name `gitea`. Do not change this, i.e. to include the version number. diff --git a/versioned_docs/version-1.19/packages/storage.md b/versioned_docs/version-1.19/packages/storage.md index 29717cf0..b09f394f 100644 --- a/versioned_docs/version-1.19/packages/storage.md +++ b/versioned_docs/version-1.19/packages/storage.md @@ -28,7 +28,7 @@ Whenever a package gets deleted only the references to the underlaying blobs are The blobs get not removed at this moment, so they still require space on the filesystem. When a new package gets uploaded the existing blobs may get referenced again. -These unreferenced blobs get deleted by a [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages). +These unreferenced blobs get deleted by a [clean up job](../administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages). The config setting `OLDER_THAN` configures how long unreferenced blobs are kept before they get deleted. ## Cleanup Rules @@ -68,7 +68,7 @@ The patterns are case-insensitive which matches the behaviour of the package reg ### How the cleanup rules work -The cleanup rules are part of the [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically. +The cleanup rules are part of the [clean up job](../administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically. The cleanup rule: diff --git a/versioned_docs/version-1.19/usage/labels.md b/versioned_docs/version-1.19/usage/labels.md index 609f7e88..cebe158a 100644 --- a/versioned_docs/version-1.19/usage/labels.md +++ b/versioned_docs/version-1.19/usage/labels.md @@ -25,7 +25,7 @@ For organizations, you can define organization-wide labels that are shared with Labels have a mandatory name, a mandatory color, an optional description, and must either be exclusive or not (see `Scoped Labels` below). -When you create a repository, you can ensure certain labels exist by using the `Issue Labels` option. This option lists a number of available label sets that are [configured globally on your instance](administration/customizing-gitea.md#labels). Its contained labels will all be created as well while creating the repository. +When you create a repository, you can ensure certain labels exist by using the `Issue Labels` option. This option lists a number of available label sets that are [configured globally on your instance](../administration/customizing-gitea.md#labels). Its contained labels will all be created as well while creating the repository. ## Scoped Labels diff --git a/versioned_docs/version-1.19/usage/linked-references.md b/versioned_docs/version-1.19/usage/linked-references.md index f2ebc9ca..ee9e3712 100644 --- a/versioned_docs/version-1.19/usage/linked-references.md +++ b/versioned_docs/version-1.19/usage/linked-references.md @@ -92,7 +92,7 @@ Sometimes a commit or pull request may fix or bring back a problem documented in a particular issue. Gitea supports closing and reopening the referenced issues by preceding the reference with a particular _keyword_. Common keywords include "closes", "fixes", "reopens", etc. This list can be -[customized](administration/config-cheat-sheet.md) by the +[customized](../administration/config-cheat-sheet.md) by the site administrator. Example: diff --git a/versioned_docs/version-1.19/usage/push.md b/versioned_docs/version-1.19/usage/push.md index f3c71b20..88bb7f2e 100644 --- a/versioned_docs/version-1.19/usage/push.md +++ b/versioned_docs/version-1.19/usage/push.md @@ -48,7 +48,7 @@ Push to create is a feature that allows you to push to a repository that does no ## Enabling Push To Create -In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#repository-repository). +In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](../administration/config-cheat-sheet.md#repository-repository). ## Using Push To Create diff --git a/versioned_docs/version-1.20/administration/cmd-embedded.md b/versioned_docs/version-1.20/administration/cmd-embedded.md index 2474da06..e1d12b20 100644 --- a/versioned_docs/version-1.20/administration/cmd-embedded.md +++ b/versioned_docs/version-1.20/administration/cmd-embedded.md @@ -19,7 +19,7 @@ menu: Gitea's executable contains all the resources required to run: templates, images, style-sheets and translations. Any of them can be overridden by placing a replacement in a matching path -inside the `custom` directory (see [Customizing Gitea](administration/customizing-gitea.md)). +inside the `custom` directory (see [Customizing Gitea](../administration/customizing-gitea.md)). To obtain a copy of the embedded resources ready for editing, the `embedded` command from the CLI can be used from the OS shell interface. @@ -85,7 +85,7 @@ The default is the current directory. The `--custom` flag tells Gitea to extract the files directly into the `custom` directory. For this to work, the command needs to know the location of the `app.ini` configuration file (`--config`) and, depending of the configuration, be ran from the directory where -Gitea normally starts. See [Customizing Gitea](administration/customizing-gitea.md) for details. +Gitea normally starts. See [Customizing Gitea](../administration/customizing-gitea.md) for details. The `--overwrite` flag allows any existing files in the destination directory to be overwritten. diff --git a/versioned_docs/version-1.20/administration/config-cheat-sheet.md b/versioned_docs/version-1.20/administration/config-cheat-sheet.md index 6e52a88b..80b18dde 100644 --- a/versioned_docs/version-1.20/administration/config-cheat-sheet.md +++ b/versioned_docs/version-1.20/administration/config-cheat-sheet.md @@ -742,7 +742,7 @@ and - `FORCE_TRUST_SERVER_CERT`: **false**: If set to `true`, completely ignores server certificate validation errors. This option is unsafe. Consider adding the certificate to the system trust store instead. - `USER`: **_empty_**: Username of mailing user (usually the sender's e-mail address). - `PASSWD`: **_empty_**: Password of mailing user. Use \`your password\` for quoting if you use special characters in the password. - - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](administration/email-setup.md) for more information. + - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](../administration/email-setup.md) for more information. - `ENABLE_HELO`: **true**: Enable HELO operation. - `HELO_HOSTNAME`: **(retrieved from system)**: HELO hostname. - `FROM`: **_empty_**: Mail from address, RFC 5322. This can be just an email address, or the "Name" \ format. diff --git a/versioned_docs/version-1.20/administration/customizing-gitea.md b/versioned_docs/version-1.20/administration/customizing-gitea.md index dbe5ea46..272372ab 100644 --- a/versioned_docs/version-1.20/administration/customizing-gitea.md +++ b/versioned_docs/version-1.20/administration/customizing-gitea.md @@ -36,7 +36,7 @@ Application settings can be found in file `CustomConf` which is by default, Again `gitea help` will allow you review this variable and you can override it using the `--config` option on the `gitea` binary. -- [Quick Cheat Sheet](administration/config-cheat-sheet.md) +- [Quick Cheat Sheet](../administration/config-cheat-sheet.md) - [Complete List](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini) If the `CustomPath` folder can't be found despite checking `gitea help`, check the `GITEA_CUSTOM` @@ -44,7 +44,7 @@ environment variable; this can be used to override the default path to something `GITEA_CUSTOM` might, for example, be set by an init script. You can check whether the value is set under the "Configuration" tab on the site administration page. -- [List of Environment Variables](administration/environment-variables.md) +- [List of Environment Variables](../administration/environment-variables.md) :::note Gitea must perform a full restart to see configuration changes. @@ -84,7 +84,7 @@ directory at the top of this document). Every single page of Gitea can be changed. Dynamic content is generated using [go templates](https://pkg.go.dev/html/template), which can be modified by placing replacements below the `$GITEA_CUSTOM/templates` directory. -To obtain any embedded file (including templates), the [`gitea embedded` tool](administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using). +To obtain any embedded file (including templates), the [`gitea embedded` tool](../administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using). Be aware that any statement contained inside `{{` and `}}` are Gitea's template syntax and shouldn't be touched without fully understanding these components. @@ -105,7 +105,7 @@ just place it under your "$GITEA_CUSTOM/public/" directory (for instance `$GITEA To match the current style, the link should have the class name "item", and you can use `{{AppSubUrl}}` to get the base URL: `Impressum` -For more information, see [Adding Legal Pages](administration/adding-legal-pages.md). +For more information, see [Adding Legal Pages](../administration/adding-legal-pages.md). You can add new tabs in the same way, putting them in `extra_tabs.tmpl`. The exact HTML needed to match the style of other tabs is in the file @@ -361,10 +361,10 @@ A full list of supported emoji's is at [emoji list](https://gitea.com/gitea/gite ## Customizing the look of Gitea The default built-in themes are `gitea` (light), `arc-green` (dark), and `auto` (chooses light or dark depending on operating system settings). -The default theme can be changed via `DEFAULT_THEME` in the [ui](administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. +The default theme can be changed via `DEFAULT_THEME` in the [ui](../administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. Gitea also has support for user themes, which means every user can select which theme should be used. -The list of themes a user can choose from can be configured with the `THEMES` value in the [ui](administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. +The list of themes a user can choose from can be configured with the `THEMES` value in the [ui](../administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. To make a custom theme available to all users: diff --git a/versioned_docs/version-1.20/administration/email-setup.md b/versioned_docs/version-1.20/administration/email-setup.md index 67950907..09f366bb 100644 --- a/versioned_docs/version-1.20/administration/email-setup.md +++ b/versioned_docs/version-1.20/administration/email-setup.md @@ -57,7 +57,7 @@ Restart Gitea for the configuration changes to take effect. To send a test email to validate the settings, go to Gitea > Site Administration > Configuration > SMTP Mailer Configuration. -For the full list of options check the [Config Cheat Sheet](administration/config-cheat-sheet.md) +For the full list of options check the [Config Cheat Sheet](../administration/config-cheat-sheet.md) :::note Authentication is only supported when the SMTP server communication is encrypted with TLS or `HOST=localhost`. TLS encryption can be through: diff --git a/versioned_docs/version-1.20/administration/external-renderers.md b/versioned_docs/version-1.20/administration/external-renderers.md index b593a154..dc0993e7 100644 --- a/versioned_docs/version-1.20/administration/external-renderers.md +++ b/versioned_docs/version-1.20/administration/external-renderers.md @@ -24,7 +24,7 @@ it is just a matter of: - add some configuration to your `app.ini` file - restart your Gitea instance -This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](administration/customizing-gitea.md) page. +This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](../administration/customizing-gitea.md) page. ## Installing external binaries diff --git a/versioned_docs/version-1.20/administration/fail2ban-setup.md b/versioned_docs/version-1.20/administration/fail2ban-setup.md index c90f88c8..0f5ac77b 100644 --- a/versioned_docs/version-1.20/administration/fail2ban-setup.md +++ b/versioned_docs/version-1.20/administration/fail2ban-setup.md @@ -119,7 +119,7 @@ proxy_set_header X-Real-IP $remote_addr; The security options in `app.ini` need to be adjusted to allow the interpretation of the headers as well as the list of IP addresses and networks that describe trusted proxy servers -(See the [configuration cheat sheet](administration/config-cheat-sheet.md#security-security) for more information). +(See the [configuration cheat sheet](../administration/config-cheat-sheet.md#security-security) for more information). ``` REVERSE_PROXY_LIMIT = 1 diff --git a/versioned_docs/version-1.20/administration/https-support.md b/versioned_docs/version-1.20/administration/https-support.md index 4e18722d..b5a08c3e 100644 --- a/versioned_docs/version-1.20/administration/https-support.md +++ b/versioned_docs/version-1.20/administration/https-support.md @@ -22,7 +22,7 @@ menu: Before you enable HTTPS, make sure that you have valid SSL/TLS certificates. You could use self-generated certificates for evaluation and testing. Please run `gitea cert --host [HOST]` to generate a self signed certificate. -If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](administration/reverse-proxies.md). +If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](../administration/reverse-proxies.md). To use Gitea's built-in HTTPS support, you must change your `app.ini` file: @@ -36,7 +36,7 @@ KEY_FILE = key.pem ``` Note that if your certificate is signed by a third party certificate authority (i.e. not self-signed), then cert.pem should contain the certificate chain. The server certificate must be the first entry in cert.pem, followed by the intermediaries in order (if any). The root certificate does not have to be included because the connecting client must already have it in order to estalbish the trust relationship. -To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](../administration/config-cheat-sheet.md#server-server). For the `CERT_FILE` or `KEY_FILE` field, the file path is relative to the `GITEA_CUSTOM` environment variable when it is a relative path. It can be an absolute path as well. @@ -85,11 +85,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](../administration/config-cheat-sheet.md#server-server). ## Using a reverse proxy -Setup up your reverse proxy as shown in the [reverse proxy guide](administration/reverse-proxies.md). +Setup up your reverse proxy as shown in the [reverse proxy guide](../administration/reverse-proxies.md). After that, enable HTTPS by following one of these guides: diff --git a/versioned_docs/version-1.20/administration/mail-templates.md b/versioned_docs/version-1.20/administration/mail-templates.md index a129453e..eee55049 100644 --- a/versioned_docs/version-1.20/administration/mail-templates.md +++ b/versioned_docs/version-1.20/administration/mail-templates.md @@ -18,7 +18,7 @@ menu: # Mail templates To craft the e-mail subject and contents for certain operations, Gitea can be customized by using templates. The templates -for these functions are located under the [`custom` directory](administration/customizing-gitea.md). +for these functions are located under the [`custom` directory](../administration/customizing-gitea.md). Gitea has an internal template that serves as default in case there's no custom alternative. Custom templates are loaded when Gitea starts. Changes made to them are not recognized until Gitea is restarted again. @@ -165,7 +165,7 @@ If the template fails to render, it will be noticed only at the moment the mail A default subject is used if the subject template fails, and whatever was rendered successfully from the the _mail body_ is used, disregarding the rest. -Please check [Gitea's logs](administration/logging-config.md) for error messages in case of trouble. +Please check [Gitea's logs](../administration/logging-config.md) for error messages in case of trouble. ## Example diff --git a/versioned_docs/version-1.20/administration/repo-indexer.md b/versioned_docs/version-1.20/administration/repo-indexer.md index 6dec2d63..66443a9b 100644 --- a/versioned_docs/version-1.20/administration/repo-indexer.md +++ b/versioned_docs/version-1.20/administration/repo-indexer.md @@ -19,7 +19,7 @@ menu: ## Setting up the repository indexer -Gitea can search through the files of the repositories by enabling this function in your [`app.ini`](administration/config-cheat-sheet.md): +Gitea can search through the files of the repositories by enabling this function in your [`app.ini`](../administration/config-cheat-sheet.md): ```ini [indexer] diff --git a/versioned_docs/version-1.20/administration/search-engines-indexation.md b/versioned_docs/version-1.20/administration/search-engines-indexation.md index 7898e814..43c59132 100644 --- a/versioned_docs/version-1.20/administration/search-engines-indexation.md +++ b/versioned_docs/version-1.20/administration/search-engines-indexation.md @@ -23,7 +23,7 @@ If you don't want your repository to be visible for search engines read further. ## Block search engines indexation using robots.txt To make Gitea serve a custom `robots.txt` (default: empty 404) for top level installations, -create a file called `robots.txt` in the [`custom` folder or `CustomPath`](administration/customizing-gitea.md) +create a file called `robots.txt` in the [`custom` folder or `CustomPath`](../administration/customizing-gitea.md) Examples on how to configure the `robots.txt` can be found at [https://moz.com/learn/seo/robotstxt](https://moz.com/learn/seo/robotstxt). diff --git a/versioned_docs/version-1.20/development/api-usage.md b/versioned_docs/version-1.20/development/api-usage.md index 465f4d38..cb3273ca 100644 --- a/versioned_docs/version-1.20/development/api-usage.md +++ b/versioned_docs/version-1.20/development/api-usage.md @@ -21,7 +21,7 @@ menu: By default, `ENABLE_SWAGGER` is true, and `MAX_RESPONSE_ITEMS` is set to 50. See [Config Cheat -Sheet](administration/config-cheat-sheet.md) for more +Sheet](../administration/config-cheat-sheet.md) for more information. ## Authentication diff --git a/versioned_docs/version-1.20/development/hacking-on-gitea.md b/versioned_docs/version-1.20/development/hacking-on-gitea.md index 2abc4b7a..acf93136 100644 --- a/versioned_docs/version-1.20/development/hacking-on-gitea.md +++ b/versioned_docs/version-1.20/development/hacking-on-gitea.md @@ -268,7 +268,7 @@ Please note you should use the Swagger 2.0 documentation, not the OpenAPI 3 docu When creating new configuration options, it is not enough to add them to the `modules/setting` files. You should add information to `custom/conf/app.ini` and to the -[configuration cheat sheet](administration/config-cheat-sheet.md) +[configuration cheat sheet](../administration/config-cheat-sheet.md) found in `docs/content/doc/administer/config-cheat-sheet.en-us.md` ### Changing the logo diff --git a/versioned_docs/version-1.20/help/faq.md b/versioned_docs/version-1.20/help/faq.md index 2fa6de7a..db7b2a3a 100644 --- a/versioned_docs/version-1.20/help/faq.md +++ b/versioned_docs/version-1.20/help/faq.md @@ -87,7 +87,7 @@ https://github.com/loganinak/MigrateGitlabToGogs There are a few places that could make this show incorrectly. -1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](administration/reverse-proxies.md) +1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](../administration/reverse-proxies.md) 2. Make sure you have correctly set `ROOT_URL` in the `server` section of your `app.ini` If certain clone options aren't showing up (HTTP/S or SSH), the following options can be checked in your `app.ini` @@ -100,7 +100,7 @@ If certain clone options aren't showing up (HTTP/S or SSH), the following option This error occurs when the reverse proxy limits the file upload size. -See the [reverse proxy guide](administration/reverse-proxies.md) for a solution with nginx. +See the [reverse proxy guide](../administration/reverse-proxies.md) for a solution with nginx. ## Custom Templates not loading or working incorrectly @@ -110,7 +110,7 @@ The correct path for the template(s) will be relative to the `CustomPath` 1. To find `CustomPath`, look for Custom File Root Path in Site Administration -> Configuration 2. If you are still unable to find a path, the default can be [calculated above](#where-does-gitea-store-what-file) -3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](administration/customizing-gitea.md) page to add your template to the correct location. +3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](../administration/customizing-gitea.md) page to add your template to the correct location. ## Does Gitea have a "GitHub/GitLab pages" feature? @@ -128,7 +128,7 @@ A "login prohibited" user is a user that is not allowed to log in to Gitea anymo ## Setting up logging -- [Official Docs](administration/logging-config.md) +- [Official Docs](../administration/logging-config.md) ## What is Swagger? @@ -151,7 +151,7 @@ There are multiple things you can combine to prevent spammers. 1. By whitelisting or blocklisting certain email domains 2. By only whitelisting certain domains with OpenID (see below) 3. Setting `ENABLE_CAPTCHA` to `true` in your `app.ini` and properly configuring `RECAPTCHA_SECRET` and `RECAPTCHA_SITEKEY` -4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI +4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](../administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI ### Only allow/block certain email domains @@ -179,7 +179,7 @@ At some point, a customer or third party needs access to a specific repo and onl ### Enable Fail2ban -Use [Fail2Ban](administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns +Use [Fail2Ban](../administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns ## How to add/use custom themes @@ -332,24 +332,24 @@ You may want to set this value to `60m` or `120m`. ## How can I create users before starting Gitea -Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](administration/command-line.md#admin) to add users like normal. +Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](../administration/command-line.md#admin) to add users like normal. ## How can I enable password reset -There is no setting for password resets. It is enabled when a [mail service](administration/email-setup.md) is configured, and disabled otherwise. +There is no setting for password resets. It is enabled when a [mail service](../administration/email-setup.md) is configured, and disabled otherwise. ## How can a user's password be changed - As an **admin**, you can change any user's password (and optionally force them to change it on next login)... - By navigating to your `Site Administration -> User Accounts` page and editing a user. - - By using the [admin CLI commands](administration/command-line.md#admin). + - By using the [admin CLI commands](../administration/command-line.md#admin). - Keep in mind most commands will also need a [global flag](administration/command-line.md#global-options) to point the CLI at the correct configuration. + Keep in mind most commands will also need a [global flag](../administration/command-line.md#global-options) to point the CLI at the correct configuration. - As a **user** you can change it... - In your account `Settings -> Account` page (this method **requires** you to know your current password). - By using the `Forgot Password` link. - If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](administration/email-setup.md). + If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](../administration/email-setup.md). ## Why is my markdown broken @@ -447,9 +447,9 @@ It is highly recommended to back-up your database before running these commands. - You can also check `/admin/config` for the repository root path. - Ensure that the user/org exists that you want to adopt repositories for. - As an admin, go to `/admin/repos/unadopted` and search. - - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository). + - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository). - If the above steps are done correctly, you should be able to select repositories to adopt. - - If no repositories are found, enable [debug logging](administration/config-cheat-sheet.md#repository) to check for any specific errors. + - If no repositories are found, enable [debug logging](../administration/config-cheat-sheet.md#repository-repository) to check for any specific errors. ## Gitea can't start on NFS diff --git a/versioned_docs/version-1.20/installation/from-binary.md b/versioned_docs/version-1.20/installation/from-binary.md index 4688d699..c5887c60 100644 --- a/versioned_docs/version-1.20/installation/from-binary.md +++ b/versioned_docs/version-1.20/installation/from-binary.md @@ -63,7 +63,7 @@ despite warnings like `This key is not certified with a trusted signature!`. ## Recommended server configuration :::note -Many of the following directories can be configured using [Environment Variables](administration/environment-variables.md) as well! +Many of the following directories can be configured using [Environment Variables](../administration/environment-variables.md) as well! Of note, configuring `GITEA_WORK_DIR` will tell Gitea where to base its working directory, as well as ease installation. ::: @@ -127,7 +127,7 @@ If you don't want the web installer to be able to write to the config file, it i * Ensure that the `SECRET_KEY` and `INTERNAL_TOKEN` values are set. (You may want to use the `gitea generate secret` to generate these secret keys.) * Ensure that any other secret keys you need are set. -See the [command line documentation](administration/command-line.md) for information on using `gitea generate secret`. +See the [command line documentation](../administration/command-line.md) for information on using `gitea generate secret`. ### Configure Gitea's working directory @@ -174,7 +174,7 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini You can update to a new version of Gitea by stopping Gitea, replacing the binary at `/usr/local/bin/gitea` and restarting the instance. The binary file name should not be changed during the update to avoid problems in existing repositories. -It is recommended that you make a [backup](administration/backup-and-restore.md) before updating your installation. +It is recommended that you make a [backup](../administration/backup-and-restore.md) before updating your installation. If you have carried out the installation steps as described above, the binary should have the generic name `gitea`. Do not change this, i.e. to include the version number. diff --git a/versioned_docs/version-1.20/installation/with-docker-rootless.md b/versioned_docs/version-1.20/installation/with-docker-rootless.md index df287c55..ddd5d8e0 100644 --- a/versioned_docs/version-1.20/installation/with-docker-rootless.md +++ b/versioned_docs/version-1.20/installation/with-docker-rootless.md @@ -256,7 +256,7 @@ documented above, please note that `db` must be used as the database hostname. ## Customization -Customization files described [here](administration/customizing-gitea.md) should +Customization files described [here](../administration/customizing-gitea.md) should be placed in `/var/lib/gitea/custom` directory. If using host volumes, it's quite easy to access these files; for named volumes, this is done through another container or by direct access at `/var/lib/docker/volumes/gitea_gitea/_/var_lib_gitea`. The configuration file will be saved at @@ -317,7 +317,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -To set required TOKEN and SECRET values, consider using Gitea's built-in [generate utility functions](administration/command-line.md#generate). +To set required TOKEN and SECRET values, consider using Gitea's built-in [generate utility functions](../administration/command-line.md#generate). # SSH Container Passthrough @@ -346,7 +346,7 @@ Once the wrapper is in place, you can make it the shell for the `git` user: sudo usermod -s /usr/local/bin/gitea-shell git ``` -Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the [SSH AuthorizedKeysCommand](administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: +Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: ```bash Match User git diff --git a/versioned_docs/version-1.20/installation/with-docker.md b/versioned_docs/version-1.20/installation/with-docker.md index 48fcf44f..2818d40e 100644 --- a/versioned_docs/version-1.20/installation/with-docker.md +++ b/versioned_docs/version-1.20/installation/with-docker.md @@ -263,7 +263,7 @@ documented above, please note that `db` must be used as the database hostname. ## Customization -Customization files described [here](administration/customizing-gitea.md) should +Customization files described [here](../administration/customizing-gitea.md) should be placed in `/data/gitea` directory. If using host volumes, it's quite easy to access these files; for named volumes, this is done through another container or by direct access at `/var/lib/docker/volumes/gitea_gitea/_data`. The configuration file will be saved at @@ -313,7 +313,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -Gitea will generate new secrets/tokens for every new installation automatically and write them into the app.ini. If you want to set the secrets/tokens manually, you can use the following docker commands to use of Gitea's built-in [generate utility functions](administration/command-line.md#generate). Do not lose/change your SECRET_KEY after the installation, otherwise the encrypted data can not be decrypted anymore. +Gitea will generate new secrets/tokens for every new installation automatically and write them into the app.ini. If you want to set the secrets/tokens manually, you can use the following docker commands to use of Gitea's built-in [generate utility functions](../administration/command-line.md#generate). Do not lose/change your SECRET_KEY after the installation, otherwise the encrypted data can not be decrypted anymore. The following commands will output a new `SECRET_KEY` and `INTERNAL_TOKEN` to `stdout`, which you can then place in your environment variables. @@ -557,7 +557,7 @@ In this option, the idea is that the host SSH uses an `AuthorizedKeysCommand` in Now all attempts to login as the `git` user on the host will be forwarded to the docker - including the `SSH_ORIGINAL_COMMAND`. We now need to set-up SSH authentication on the host. -We will do this by leveraging the [SSH AuthorizedKeysCommand](administration/command-line.md#keys) to match the keys against those accepted by Gitea. +We will do this by leveraging the [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: diff --git a/versioned_docs/version-1.20/search.md b/versioned_docs/version-1.20/search.md deleted file mode 100644 index 226d9fe3..00000000 --- a/versioned_docs/version-1.20/search.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -date: "2019-11-12T16:00:00+02:00" -title: "Search" -slug: "search" -sidebar_position: 1 -toc: false -draft: false -aliases: - - /en-us/help/search -sitemap: - priority : 1 -layout: "search" ---- - -This file exists solely to respond to /search URL with the related `search` layout template. - -No content shown here is rendered, all content is based in the template layouts/doc/search.html - -Setting a very low sitemap priority will tell search engines this is not important content. diff --git a/versioned_docs/version-1.20/usage/actions/comparison.md b/versioned_docs/version-1.20/usage/actions/comparison.md index 8ff883df..5b60c8e7 100644 --- a/versioned_docs/version-1.20/usage/actions/comparison.md +++ b/versioned_docs/version-1.20/usage/actions/comparison.md @@ -128,7 +128,7 @@ The missing host will be filled with `https://gitea.com` if you don't configure That means `uses: actions/checkout@v3` will download the action from [gitea.com/actions/checkout](https://gitea.com/actions/checkout), instead of [github.com/actions/checkout](https://github.com/actions/checkout). As mentioned, it's configurable. -If you want your runners to download actions from GitHub or your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`. See [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions). +If you want your runners to download actions from GitHub or your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`. See [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions). ### Context availability diff --git a/versioned_docs/version-1.20/usage/actions/faq.md b/versioned_docs/version-1.20/usage/actions/faq.md index 1d598729..25e0ff14 100644 --- a/versioned_docs/version-1.20/usage/actions/faq.md +++ b/versioned_docs/version-1.20/usage/actions/faq.md @@ -61,7 +61,7 @@ For example: Be careful, the `https://` or `http://` prefix is necessary! Alternatively, if you want your runners to download actions from GitHub or your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`. -See [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions). +See [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions). This is one of the differences from GitHub Actions, but it should allow users much more flexibility in how they run Actions. diff --git a/versioned_docs/version-1.20/usage/actions/quickstart.md b/versioned_docs/version-1.20/usage/actions/quickstart.md index dcc83118..eb4acb35 100644 --- a/versioned_docs/version-1.20/usage/actions/quickstart.md +++ b/versioned_docs/version-1.20/usage/actions/quickstart.md @@ -30,7 +30,7 @@ Actions are disabled by default, so you need to add the following to the configu ENABLED=true ``` -If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions). +If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions). ### Set up runner @@ -125,7 +125,7 @@ That is because Gitea Actions is designed to be compatible with GitHub Actions Be careful, the demo file contains some emojis. Please make sure your database supports them, especially when using MySQL. If the charset is not `utf8mb4`, errors will occur, such as `Error 1366 (HY000): Incorrect string value: '\\xF0\\x9F\\x8E\\x89 T...' for column 'name' at row 1`. -See [Database Preparation](installation/database-preparation.md#mysql) for more information. +See [Database Preparation](../../installation/database-preparation.md#mysqlmariadb) for more information. Alternatively, you can remove all emojis from the demo file and try again. diff --git a/versioned_docs/version-1.20/usage/linked-references.md b/versioned_docs/version-1.20/usage/linked-references.md index a0acb024..b6f733dd 100644 --- a/versioned_docs/version-1.20/usage/linked-references.md +++ b/versioned_docs/version-1.20/usage/linked-references.md @@ -94,7 +94,7 @@ Sometimes a commit or pull request may fix or bring back a problem documented in a particular issue. Gitea supports closing and reopening the referenced issues by preceding the reference with a particular _keyword_. Common keywords include "closes", "fixes", "reopens", etc. This list can be -[customized](administration/config-cheat-sheet.md) by the +[customized](../administration/config-cheat-sheet.md) by the site administrator. Example: diff --git a/versioned_docs/version-1.20/usage/packages/storage.md b/versioned_docs/version-1.20/usage/packages/storage.md index f437412d..3db44aaa 100644 --- a/versioned_docs/version-1.20/usage/packages/storage.md +++ b/versioned_docs/version-1.20/usage/packages/storage.md @@ -28,7 +28,7 @@ Whenever a package gets deleted, only the references to the underlying blobs are The blobs get not removed at this moment, so they still require space on the filesystem. When a new package gets uploaded the existing blobs may get referenced again. -These unreferenced blobs get deleted by a [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages). +These unreferenced blobs get deleted by a [clean up job](../../administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages). The config setting `OLDER_THAN` configures how long unreferenced blobs are kept before they get deleted. ## Cleanup Rules @@ -68,7 +68,7 @@ The patterns are case-insensitive which matches the behaviour of the package reg ### How the cleanup rules work -The cleanup rules are part of the [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically. +The cleanup rules are part of the [clean up job](../../administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically. The cleanup rule: diff --git a/versioned_docs/version-1.20/usage/push.md b/versioned_docs/version-1.20/usage/push.md index d88dc1a2..a8c87a46 100644 --- a/versioned_docs/version-1.20/usage/push.md +++ b/versioned_docs/version-1.20/usage/push.md @@ -51,7 +51,7 @@ Push to create is a feature that allows you to push to a repository that does no ## Enabling Push To Create -In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#repository-repository). +In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](../administration/config-cheat-sheet.md#repository-repository). ## Using Push To Create diff --git a/versioned_docs/version-1.21/administration/cmd-embedded.md b/versioned_docs/version-1.21/administration/cmd-embedded.md index a7a4db72..1ee09626 100644 --- a/versioned_docs/version-1.21/administration/cmd-embedded.md +++ b/versioned_docs/version-1.21/administration/cmd-embedded.md @@ -19,7 +19,7 @@ menu: Gitea's executable contains all the resources required to run: templates, images, style-sheets and translations. Any of them can be overridden by placing a replacement in a matching path -inside the `custom` directory (see [Customizing Gitea](administration/customizing-gitea.md)). +inside the `custom` directory (see [Customizing Gitea](../administration/customizing-gitea.md)). To obtain a copy of the embedded resources ready for editing, the `embedded` command from the CLI can be used from the OS shell interface. @@ -85,7 +85,7 @@ The default is the current directory. The `--custom` flag tells Gitea to extract the files directly into the `custom` directory. For this to work, the command needs to know the location of the `app.ini` configuration file (`--config`) and, depending of the configuration, be ran from the directory where -Gitea normally starts. See [Customizing Gitea](administration/customizing-gitea.md) for details. +Gitea normally starts. See [Customizing Gitea](../administration/customizing-gitea.md) for details. The `--overwrite` flag allows any existing files in the destination directory to be overwritten. diff --git a/versioned_docs/version-1.21/administration/config-cheat-sheet.md b/versioned_docs/version-1.21/administration/config-cheat-sheet.md index 37d58d38..2b0cddce 100644 --- a/versioned_docs/version-1.21/administration/config-cheat-sheet.md +++ b/versioned_docs/version-1.21/administration/config-cheat-sheet.md @@ -745,7 +745,7 @@ and - `FORCE_TRUST_SERVER_CERT`: **false**: If set to `true`, completely ignores server certificate validation errors. This option is unsafe. Consider adding the certificate to the system trust store instead. - `USER`: **_empty_**: Username of mailing user (usually the sender's e-mail address). - `PASSWD`: **_empty_**: Password of mailing user. Use \`your password\` for quoting if you use special characters in the password. - - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](administration/email-setup.md) for more information. + - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](../administration/email-setup.md) for more information. - `ENABLE_HELO`: **true**: Enable HELO operation. - `HELO_HOSTNAME`: **(retrieved from system)**: HELO hostname. - `FROM`: **_empty_**: Mail from address, RFC 5322. This can be just an email address, or the "Name" \ format. diff --git a/versioned_docs/version-1.21/administration/customizing-gitea.md b/versioned_docs/version-1.21/administration/customizing-gitea.md index 36d5f0d4..16b4ed8a 100644 --- a/versioned_docs/version-1.21/administration/customizing-gitea.md +++ b/versioned_docs/version-1.21/administration/customizing-gitea.md @@ -36,7 +36,7 @@ Application settings can be found in file `CustomConf` which is by default, Again `gitea help` will allow you review this variable and you can override it using the `--config` option on the `gitea` binary. -- [Quick Cheat Sheet](administration/config-cheat-sheet.md) +- [Quick Cheat Sheet](../administration/config-cheat-sheet.md) - [Complete List](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini) If the `CustomPath` folder can't be found despite checking `gitea help`, check the `GITEA_CUSTOM` @@ -44,7 +44,7 @@ environment variable; this can be used to override the default path to something `GITEA_CUSTOM` might, for example, be set by an init script. You can check whether the value is set under the "Configuration" tab on the site administration page. -- [List of Environment Variables](administration/environment-variables.md) +- [List of Environment Variables](../administration/environment-variables.md) :::note Gitea must perform a full restart to see configuration changes. @@ -89,7 +89,7 @@ directory at the top of this document). Every single page of Gitea can be changed. Dynamic content is generated using [go templates](https://pkg.go.dev/html/template), which can be modified by placing replacements below the `$GITEA_CUSTOM/templates` directory. -To obtain any embedded file (including templates), the [`gitea embedded` tool](administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using). +To obtain any embedded file (including templates), the [`gitea embedded` tool](../administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using). Be aware that any statement contained inside `{{` and `}}` are Gitea's template syntax and shouldn't be touched without fully understanding these components. @@ -110,7 +110,7 @@ just place it under your "$GITEA_CUSTOM/public/assets/" directory (for instance To match the current style, the link should have the class name "item", and you can use `{{AppSubUrl}}` to get the base URL: `Impressum` -For more information, see [Adding Legal Pages](administration/adding-legal-pages.md). +For more information, see [Adding Legal Pages](../administration/adding-legal-pages.md). You can add new tabs in the same way, putting them in `extra_tabs.tmpl`. The exact HTML needed to match the style of other tabs is in the file @@ -377,10 +377,10 @@ A full list of supported emoji's is at [emoji list](https://gitea.com/gitea/gite ## Customizing the look of Gitea The default built-in themes are `gitea` (light), `arc-green` (dark), and `auto` (chooses light or dark depending on operating system settings). -The default theme can be changed via `DEFAULT_THEME` in the [ui](administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. +The default theme can be changed via `DEFAULT_THEME` in the [ui](../administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. Gitea also has support for user themes, which means every user can select which theme should be used. -The list of themes a user can choose from can be configured with the `THEMES` value in the [ui](administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. +The list of themes a user can choose from can be configured with the `THEMES` value in the [ui](../administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. To make a custom theme available to all users: diff --git a/versioned_docs/version-1.21/administration/email-setup.md b/versioned_docs/version-1.21/administration/email-setup.md index 690d8041..1c8b3b99 100644 --- a/versioned_docs/version-1.21/administration/email-setup.md +++ b/versioned_docs/version-1.21/administration/email-setup.md @@ -55,7 +55,7 @@ Restart Gitea for the configuration changes to take effect. To send a test email to validate the settings, go to Gitea > Site Administration > Configuration > SMTP Mailer Configuration. -For the full list of options check the [Config Cheat Sheet](administration/config-cheat-sheet.md) +For the full list of options check the [Config Cheat Sheet](../administration/config-cheat-sheet.md) Please note: authentication is only supported when the SMTP server communication is encrypted with TLS or `HOST=localhost`. TLS encryption can be through: diff --git a/versioned_docs/version-1.21/administration/external-renderers.md b/versioned_docs/version-1.21/administration/external-renderers.md index 1e41b801..8972fe65 100644 --- a/versioned_docs/version-1.21/administration/external-renderers.md +++ b/versioned_docs/version-1.21/administration/external-renderers.md @@ -24,7 +24,7 @@ it is just a matter of: - add some configuration to your `app.ini` file - restart your Gitea instance -This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](administration/customizing-gitea.md) page. +This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](../administration/customizing-gitea.md) page. ## Installing external binaries diff --git a/versioned_docs/version-1.21/administration/fail2ban-setup.md b/versioned_docs/version-1.21/administration/fail2ban-setup.md index c90f88c8..0f5ac77b 100644 --- a/versioned_docs/version-1.21/administration/fail2ban-setup.md +++ b/versioned_docs/version-1.21/administration/fail2ban-setup.md @@ -119,7 +119,7 @@ proxy_set_header X-Real-IP $remote_addr; The security options in `app.ini` need to be adjusted to allow the interpretation of the headers as well as the list of IP addresses and networks that describe trusted proxy servers -(See the [configuration cheat sheet](administration/config-cheat-sheet.md#security-security) for more information). +(See the [configuration cheat sheet](../administration/config-cheat-sheet.md#security-security) for more information). ``` REVERSE_PROXY_LIMIT = 1 diff --git a/versioned_docs/version-1.21/administration/https-support.md b/versioned_docs/version-1.21/administration/https-support.md index 4e18722d..b5a08c3e 100644 --- a/versioned_docs/version-1.21/administration/https-support.md +++ b/versioned_docs/version-1.21/administration/https-support.md @@ -22,7 +22,7 @@ menu: Before you enable HTTPS, make sure that you have valid SSL/TLS certificates. You could use self-generated certificates for evaluation and testing. Please run `gitea cert --host [HOST]` to generate a self signed certificate. -If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](administration/reverse-proxies.md). +If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](../administration/reverse-proxies.md). To use Gitea's built-in HTTPS support, you must change your `app.ini` file: @@ -36,7 +36,7 @@ KEY_FILE = key.pem ``` Note that if your certificate is signed by a third party certificate authority (i.e. not self-signed), then cert.pem should contain the certificate chain. The server certificate must be the first entry in cert.pem, followed by the intermediaries in order (if any). The root certificate does not have to be included because the connecting client must already have it in order to estalbish the trust relationship. -To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](../administration/config-cheat-sheet.md#server-server). For the `CERT_FILE` or `KEY_FILE` field, the file path is relative to the `GITEA_CUSTOM` environment variable when it is a relative path. It can be an absolute path as well. @@ -85,11 +85,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](../administration/config-cheat-sheet.md#server-server). ## Using a reverse proxy -Setup up your reverse proxy as shown in the [reverse proxy guide](administration/reverse-proxies.md). +Setup up your reverse proxy as shown in the [reverse proxy guide](../administration/reverse-proxies.md). After that, enable HTTPS by following one of these guides: diff --git a/versioned_docs/version-1.21/administration/mail-templates.md b/versioned_docs/version-1.21/administration/mail-templates.md index a129453e..eee55049 100644 --- a/versioned_docs/version-1.21/administration/mail-templates.md +++ b/versioned_docs/version-1.21/administration/mail-templates.md @@ -18,7 +18,7 @@ menu: # Mail templates To craft the e-mail subject and contents for certain operations, Gitea can be customized by using templates. The templates -for these functions are located under the [`custom` directory](administration/customizing-gitea.md). +for these functions are located under the [`custom` directory](../administration/customizing-gitea.md). Gitea has an internal template that serves as default in case there's no custom alternative. Custom templates are loaded when Gitea starts. Changes made to them are not recognized until Gitea is restarted again. @@ -165,7 +165,7 @@ If the template fails to render, it will be noticed only at the moment the mail A default subject is used if the subject template fails, and whatever was rendered successfully from the the _mail body_ is used, disregarding the rest. -Please check [Gitea's logs](administration/logging-config.md) for error messages in case of trouble. +Please check [Gitea's logs](../administration/logging-config.md) for error messages in case of trouble. ## Example diff --git a/versioned_docs/version-1.21/administration/repo-indexer.md b/versioned_docs/version-1.21/administration/repo-indexer.md index 6dec2d63..66443a9b 100644 --- a/versioned_docs/version-1.21/administration/repo-indexer.md +++ b/versioned_docs/version-1.21/administration/repo-indexer.md @@ -19,7 +19,7 @@ menu: ## Setting up the repository indexer -Gitea can search through the files of the repositories by enabling this function in your [`app.ini`](administration/config-cheat-sheet.md): +Gitea can search through the files of the repositories by enabling this function in your [`app.ini`](../administration/config-cheat-sheet.md): ```ini [indexer] diff --git a/versioned_docs/version-1.21/administration/search-engines-indexation.md b/versioned_docs/version-1.21/administration/search-engines-indexation.md index 7898e814..43c59132 100644 --- a/versioned_docs/version-1.21/administration/search-engines-indexation.md +++ b/versioned_docs/version-1.21/administration/search-engines-indexation.md @@ -23,7 +23,7 @@ If you don't want your repository to be visible for search engines read further. ## Block search engines indexation using robots.txt To make Gitea serve a custom `robots.txt` (default: empty 404) for top level installations, -create a file called `robots.txt` in the [`custom` folder or `CustomPath`](administration/customizing-gitea.md) +create a file called `robots.txt` in the [`custom` folder or `CustomPath`](../administration/customizing-gitea.md) Examples on how to configure the `robots.txt` can be found at [https://moz.com/learn/seo/robotstxt](https://moz.com/learn/seo/robotstxt). diff --git a/versioned_docs/version-1.21/development/api-usage.md b/versioned_docs/version-1.21/development/api-usage.md index 94dac70b..1209b8e1 100644 --- a/versioned_docs/version-1.21/development/api-usage.md +++ b/versioned_docs/version-1.21/development/api-usage.md @@ -19,7 +19,7 @@ menu: ## Enabling/configuring API access -By default, `ENABLE_SWAGGER` is true, and `MAX_RESPONSE_ITEMS` is set to 50. See [Config Cheat Sheet](administration/config-cheat-sheet.md) for more information. +By default, `ENABLE_SWAGGER` is true, and `MAX_RESPONSE_ITEMS` is set to 50. See [Config Cheat Sheet](../administration/config-cheat-sheet.md) for more information. ## Authentication diff --git a/versioned_docs/version-1.21/development/hacking-on-gitea.md b/versioned_docs/version-1.21/development/hacking-on-gitea.md index 46b781ad..f4d06b10 100644 --- a/versioned_docs/version-1.21/development/hacking-on-gitea.md +++ b/versioned_docs/version-1.21/development/hacking-on-gitea.md @@ -271,7 +271,7 @@ Please note you should use the Swagger 2.0 documentation, not the OpenAPI 3 docu When creating new configuration options, it is not enough to add them to the `modules/setting` files. You should add information to `custom/conf/app.ini` and to the -[configuration cheat sheet](administration/config-cheat-sheet.md) +[configuration cheat sheet](../administration/config-cheat-sheet.md) found in `docs/content/doc/administer/config-cheat-sheet.en-us.md` ### Changing the logo diff --git a/versioned_docs/version-1.21/help/faq.md b/versioned_docs/version-1.21/help/faq.md index 74a6c0bf..73bd5a8f 100644 --- a/versioned_docs/version-1.21/help/faq.md +++ b/versioned_docs/version-1.21/help/faq.md @@ -87,7 +87,7 @@ https://github.com/loganinak/MigrateGitlabToGogs There are a few places that could make this show incorrectly. -1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](administration/reverse-proxies.md) +1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](../administration/reverse-proxies.md) 2. Make sure you have correctly set `ROOT_URL` in the `server` section of your `app.ini` If certain clone options aren't showing up (HTTP/S or SSH), the following options can be checked in your `app.ini` @@ -100,7 +100,7 @@ If certain clone options aren't showing up (HTTP/S or SSH), the following option This error occurs when the reverse proxy limits the file upload size. -See the [reverse proxy guide](administration/reverse-proxies.md) for a solution with nginx. +See the [reverse proxy guide](../administration/reverse-proxies.md) for a solution with nginx. ## Custom Templates not loading or working incorrectly @@ -110,7 +110,7 @@ The correct path for the template(s) will be relative to the `CustomPath` 1. To find `CustomPath`, look for Custom File Root Path in Site Administration -> Configuration 2. If you are still unable to find a path, the default can be [calculated above](#where-does-gitea-store-what-file) -3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](administration/customizing-gitea.md) page to add your template to the correct location. +3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](../administration/customizing-gitea.md) page to add your template to the correct location. ## Does Gitea have a "GitHub/GitLab pages" feature? @@ -128,7 +128,7 @@ A "login prohibited" user is a user that is not allowed to log in to Gitea anymo ## Setting up logging -- [Official Docs](administration/logging-config.md) +- [Official Docs](../administration/logging-config.md) ## What is Swagger? @@ -151,7 +151,7 @@ There are multiple things you can combine to prevent spammers. 1. By whitelisting or blocklisting certain email domains 2. By only whitelisting certain domains with OpenID (see below) 3. Setting `ENABLE_CAPTCHA` to `true` in your `app.ini` and properly configuring `RECAPTCHA_SECRET` and `RECAPTCHA_SITEKEY` -4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI +4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](../administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI ### Only allow/block certain email domains @@ -179,7 +179,7 @@ At some point, a customer or third party needs access to a specific repo and onl ### Enable Fail2ban -Use [Fail2Ban](administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns +Use [Fail2Ban](../administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns ## How to add/use custom themes @@ -334,24 +334,24 @@ You may want to set this value to `60m` or `120m`. ## How can I create users before starting Gitea -Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](administration/command-line.md#admin) to add users like normal. +Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](../administration/command-line.md#admin) to add users like normal. ## How can I enable password reset -There is no setting for password resets. It is enabled when a [mail service](administration/email-setup.md) is configured, and disabled otherwise. +There is no setting for password resets. It is enabled when a [mail service](../administration/email-setup.md) is configured, and disabled otherwise. ## How can a user's password be changed - As an **admin**, you can change any user's password (and optionally force them to change it on next login)... - By navigating to your `Site Administration -> User Accounts` page and editing a user. - - By using the [admin CLI commands](administration/command-line.md#admin). + - By using the [admin CLI commands](../administration/command-line.md#admin). - Keep in mind most commands will also need a [global flag](administration/command-line.md#global-options) to point the CLI at the correct configuration. + Keep in mind most commands will also need a [global flag](../administration/command-line.md#global-options) to point the CLI at the correct configuration. - As a **user** you can change it... - In your account `Settings -> Account` page (this method **requires** you to know your current password). - By using the `Forgot Password` link. - If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](administration/email-setup.md). + If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](../administration/email-setup.md). ## Why is my markdown broken @@ -447,9 +447,9 @@ It is highly recommended to back-up your database before running these commands. - You can also check `/admin/config` for the repository root path. - Ensure that the user/org exists that you want to adopt repositories for. - As an admin, go to `/admin/repos/unadopted` and search. - - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository). + - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository). - If the above steps are done correctly, you should be able to select repositories to adopt. - - If no repositories are found, enable [debug logging](administration/config-cheat-sheet.md#repository) to check for any specific errors. + - If no repositories are found, enable [debug logging](../administration/config-cheat-sheet.md#repository-repository) to check for any specific errors. ## Gitea can't start on NFS diff --git a/versioned_docs/version-1.21/index.md b/versioned_docs/version-1.21/index.md index 919bdabe..8441c62b 100644 --- a/versioned_docs/version-1.21/index.md +++ b/versioned_docs/version-1.21/index.md @@ -15,7 +15,7 @@ blog post to read about the justification for a fork. :::warning -Gitea has never sent commits to upstream or cherry-pick commits from upstream. So Gitea is totally not compatible with Gogs. No any gurantee it can work if you upgrade from Gogs to Gitea. The recommands method is to migrate repositories from Gogs to Gitea. +Gitea has never sent commits to upstream or cherry-pick commits from upstream. So Gitea is totally not compatible with Gogs. No any gurantee it can work if you upgrade from Gogs to Gitea. The recommanded method is to migrate repositories from Gogs to Gitea. ::: diff --git a/versioned_docs/version-1.21/installation/database-preparation.md b/versioned_docs/version-1.21/installation/database-preparation.md index 5e0b9466..122c7e53 100644 --- a/versioned_docs/version-1.21/installation/database-preparation.md +++ b/versioned_docs/version-1.21/installation/database-preparation.md @@ -35,7 +35,7 @@ Note: All steps below requires that the database engine of your choice is instal 2. On database instance, login to database console as root: - ``` + ```shell mysql -u root -p ``` diff --git a/versioned_docs/version-1.21/installation/from-binary.md b/versioned_docs/version-1.21/installation/from-binary.md index 4688d699..c5887c60 100644 --- a/versioned_docs/version-1.21/installation/from-binary.md +++ b/versioned_docs/version-1.21/installation/from-binary.md @@ -63,7 +63,7 @@ despite warnings like `This key is not certified with a trusted signature!`. ## Recommended server configuration :::note -Many of the following directories can be configured using [Environment Variables](administration/environment-variables.md) as well! +Many of the following directories can be configured using [Environment Variables](../administration/environment-variables.md) as well! Of note, configuring `GITEA_WORK_DIR` will tell Gitea where to base its working directory, as well as ease installation. ::: @@ -127,7 +127,7 @@ If you don't want the web installer to be able to write to the config file, it i * Ensure that the `SECRET_KEY` and `INTERNAL_TOKEN` values are set. (You may want to use the `gitea generate secret` to generate these secret keys.) * Ensure that any other secret keys you need are set. -See the [command line documentation](administration/command-line.md) for information on using `gitea generate secret`. +See the [command line documentation](../administration/command-line.md) for information on using `gitea generate secret`. ### Configure Gitea's working directory @@ -174,7 +174,7 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini You can update to a new version of Gitea by stopping Gitea, replacing the binary at `/usr/local/bin/gitea` and restarting the instance. The binary file name should not be changed during the update to avoid problems in existing repositories. -It is recommended that you make a [backup](administration/backup-and-restore.md) before updating your installation. +It is recommended that you make a [backup](../administration/backup-and-restore.md) before updating your installation. If you have carried out the installation steps as described above, the binary should have the generic name `gitea`. Do not change this, i.e. to include the version number. diff --git a/versioned_docs/version-1.21/installation/with-docker-rootless.md b/versioned_docs/version-1.21/installation/with-docker-rootless.md index 452179fc..21bcf192 100644 --- a/versioned_docs/version-1.21/installation/with-docker-rootless.md +++ b/versioned_docs/version-1.21/installation/with-docker-rootless.md @@ -256,7 +256,7 @@ documented above, please note that `db` must be used as the database hostname. ## Customization -Customization files described [here](administration/customizing-gitea.md) should +Customization files described [here](../administration/customizing-gitea.md) should be placed in `/var/lib/gitea/custom` directory. If using host volumes, it's quite easy to access these files; for named volumes, this is done through another container or by direct access at `/var/lib/docker/volumes/gitea_gitea/_/var_lib_gitea`. The configuration file will be saved at @@ -317,7 +317,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -To set required TOKEN and SECRET values, consider using Gitea's built-in [generate utility functions](administration/command-line.md#generate). +To set required TOKEN and SECRET values, consider using Gitea's built-in [generate utility functions](../administration/command-line.md#generate). # SSH Container Passthrough @@ -346,7 +346,7 @@ Once the wrapper is in place, you can make it the shell for the `git` user: sudo usermod -s /usr/local/bin/gitea-shell git ``` -Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the [SSH AuthorizedKeysCommand](administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: +Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: ```bash Match User git diff --git a/versioned_docs/version-1.21/installation/with-docker.md b/versioned_docs/version-1.21/installation/with-docker.md index 8f070496..aa24fdb9 100644 --- a/versioned_docs/version-1.21/installation/with-docker.md +++ b/versioned_docs/version-1.21/installation/with-docker.md @@ -263,7 +263,7 @@ documented above, please note that `db` must be used as the database hostname. ## Customization -Customization files described [here](administration/customizing-gitea.md) should +Customization files described [here](../administration/customizing-gitea.md) should be placed in `/data/gitea` directory. If using host volumes, it's quite easy to access these files; for named volumes, this is done through another container or by direct access at `/var/lib/docker/volumes/gitea_gitea/_data`. The configuration file will be saved at @@ -313,7 +313,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -Gitea will generate new secrets/tokens for every new installation automatically and write them into the app.ini. If you want to set the secrets/tokens manually, you can use the following docker commands to use of Gitea's built-in [generate utility functions](administration/command-line.md#generate). Do not lose/change your SECRET_KEY after the installation, otherwise the encrypted data can not be decrypted anymore. +Gitea will generate new secrets/tokens for every new installation automatically and write them into the app.ini. If you want to set the secrets/tokens manually, you can use the following docker commands to use of Gitea's built-in [generate utility functions](../administration/command-line.md#generate). Do not lose/change your SECRET_KEY after the installation, otherwise the encrypted data can not be decrypted anymore. The following commands will output a new `SECRET_KEY` and `INTERNAL_TOKEN` to `stdout`, which you can then place in your environment variables. @@ -557,7 +557,7 @@ In this option, the idea is that the host SSH uses an `AuthorizedKeysCommand` in Now all attempts to login as the `git` user on the host will be forwarded to the docker - including the `SSH_ORIGINAL_COMMAND`. We now need to set-up SSH authentication on the host. -We will do this by leveraging the [SSH AuthorizedKeysCommand](administration/command-line.md#keys) to match the keys against those accepted by Gitea. +We will do this by leveraging the [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: diff --git a/versioned_docs/version-1.21/search.md b/versioned_docs/version-1.21/search.md deleted file mode 100644 index 226d9fe3..00000000 --- a/versioned_docs/version-1.21/search.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -date: "2019-11-12T16:00:00+02:00" -title: "Search" -slug: "search" -sidebar_position: 1 -toc: false -draft: false -aliases: - - /en-us/help/search -sitemap: - priority : 1 -layout: "search" ---- - -This file exists solely to respond to /search URL with the related `search` layout template. - -No content shown here is rendered, all content is based in the template layouts/doc/search.html - -Setting a very low sitemap priority will tell search engines this is not important content. diff --git a/versioned_docs/version-1.21/usage/actions/act-runner.md b/versioned_docs/version-1.21/usage/actions/act-runner.md index bd0dc1a9..909d9fe3 100644 --- a/versioned_docs/version-1.21/usage/actions/act-runner.md +++ b/versioned_docs/version-1.21/usage/actions/act-runner.md @@ -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.md#actions-generate-runner-token): +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 diff --git a/versioned_docs/version-1.21/usage/actions/comparison.md b/versioned_docs/version-1.21/usage/actions/comparison.md index 4d725f7a..c179489b 100644 --- a/versioned_docs/version-1.21/usage/actions/comparison.md +++ b/versioned_docs/version-1.21/usage/actions/comparison.md @@ -132,7 +132,7 @@ If you want to download an action from another git hoster, you can use an absolu If your Gitea instance is in an intranet or a restricted area, you can set the URL to `self` to only download actions from your own instance by default. Of course, you can still use absolute URLs in workflows. -More details about the `[actions].DEFAULT_ACTIONS_URL` configuration can be found in the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions)。 +More details about the `[actions].DEFAULT_ACTIONS_URL` configuration can be found in the [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions)。 ### Context availability diff --git a/versioned_docs/version-1.21/usage/actions/faq.md b/versioned_docs/version-1.21/usage/actions/faq.md index 427d57c4..c4671947 100644 --- a/versioned_docs/version-1.21/usage/actions/faq.md +++ b/versioned_docs/version-1.21/usage/actions/faq.md @@ -62,7 +62,7 @@ This is one of the differences from GitHub Actions which supports actions script But it should allow users much more flexibility in how they run Actions. Alternatively, if you want your runners to download actions from your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`. -See [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions). +See [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions). ## How to limit the permission of the runners? diff --git a/versioned_docs/version-1.21/usage/actions/quickstart.md b/versioned_docs/version-1.21/usage/actions/quickstart.md index f7f4ee2c..943c81c2 100644 --- a/versioned_docs/version-1.21/usage/actions/quickstart.md +++ b/versioned_docs/version-1.21/usage/actions/quickstart.md @@ -30,7 +30,7 @@ Since 1.21.0, Actions are enabled by default. If you are using versions before 1 ENABLED=true ``` -If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions). +If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions). ### Set up runner @@ -129,7 +129,7 @@ That is because Gitea Actions is designed to be compatible with GitHub Actions Be careful, the demo file contains some emojis. Please make sure your database supports them, especially when using MySQL. If the charset is not `utf8mb4`, errors will occur, such as `Error 1366 (HY000): Incorrect string value: '\\xF0\\x9F\\x8E\\x89 T...' for column 'name' at row 1`. -See [Database Preparation](installation/database-preparation.md#mysql) for more information. +See [Database Preparation](../../installation/database-preparation.md#mysqlmariadb) for more information. Alternatively, you can remove all emojis from the demo file and try again. diff --git a/versioned_docs/version-1.21/usage/linked-references.md b/versioned_docs/version-1.21/usage/linked-references.md index a0acb024..b6f733dd 100644 --- a/versioned_docs/version-1.21/usage/linked-references.md +++ b/versioned_docs/version-1.21/usage/linked-references.md @@ -94,7 +94,7 @@ Sometimes a commit or pull request may fix or bring back a problem documented in a particular issue. Gitea supports closing and reopening the referenced issues by preceding the reference with a particular _keyword_. Common keywords include "closes", "fixes", "reopens", etc. This list can be -[customized](administration/config-cheat-sheet.md) by the +[customized](../administration/config-cheat-sheet.md) by the site administrator. Example: diff --git a/versioned_docs/version-1.21/usage/packages/storage.md b/versioned_docs/version-1.21/usage/packages/storage.md index f437412d..3db44aaa 100644 --- a/versioned_docs/version-1.21/usage/packages/storage.md +++ b/versioned_docs/version-1.21/usage/packages/storage.md @@ -28,7 +28,7 @@ Whenever a package gets deleted, only the references to the underlying blobs are The blobs get not removed at this moment, so they still require space on the filesystem. When a new package gets uploaded the existing blobs may get referenced again. -These unreferenced blobs get deleted by a [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages). +These unreferenced blobs get deleted by a [clean up job](../../administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages). The config setting `OLDER_THAN` configures how long unreferenced blobs are kept before they get deleted. ## Cleanup Rules @@ -68,7 +68,7 @@ The patterns are case-insensitive which matches the behaviour of the package reg ### How the cleanup rules work -The cleanup rules are part of the [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically. +The cleanup rules are part of the [clean up job](../../administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically. The cleanup rule: diff --git a/versioned_docs/version-1.21/usage/push.md b/versioned_docs/version-1.21/usage/push.md index d88dc1a2..a8c87a46 100644 --- a/versioned_docs/version-1.21/usage/push.md +++ b/versioned_docs/version-1.21/usage/push.md @@ -51,7 +51,7 @@ Push to create is a feature that allows you to push to a repository that does no ## Enabling Push To Create -In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#repository-repository). +In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](../administration/config-cheat-sheet.md#repository-repository). ## Using Push To Create diff --git a/versioned_docs/version-1.22/administration/cmd-embedded.md b/versioned_docs/version-1.22/administration/cmd-embedded.md index a7a4db72..1ee09626 100644 --- a/versioned_docs/version-1.22/administration/cmd-embedded.md +++ b/versioned_docs/version-1.22/administration/cmd-embedded.md @@ -19,7 +19,7 @@ menu: Gitea's executable contains all the resources required to run: templates, images, style-sheets and translations. Any of them can be overridden by placing a replacement in a matching path -inside the `custom` directory (see [Customizing Gitea](administration/customizing-gitea.md)). +inside the `custom` directory (see [Customizing Gitea](../administration/customizing-gitea.md)). To obtain a copy of the embedded resources ready for editing, the `embedded` command from the CLI can be used from the OS shell interface. @@ -85,7 +85,7 @@ The default is the current directory. The `--custom` flag tells Gitea to extract the files directly into the `custom` directory. For this to work, the command needs to know the location of the `app.ini` configuration file (`--config`) and, depending of the configuration, be ran from the directory where -Gitea normally starts. See [Customizing Gitea](administration/customizing-gitea.md) for details. +Gitea normally starts. See [Customizing Gitea](../administration/customizing-gitea.md) for details. The `--overwrite` flag allows any existing files in the destination directory to be overwritten. diff --git a/versioned_docs/version-1.22/administration/config-cheat-sheet.md b/versioned_docs/version-1.22/administration/config-cheat-sheet.md index 8763a11c..d822b697 100644 --- a/versioned_docs/version-1.22/administration/config-cheat-sheet.md +++ b/versioned_docs/version-1.22/administration/config-cheat-sheet.md @@ -762,7 +762,7 @@ and - `FORCE_TRUST_SERVER_CERT`: **false**: If set to `true`, completely ignores server certificate validation errors. This option is unsafe. Consider adding the certificate to the system trust store instead. - `USER`: **_empty_**: Username of mailing user (usually the sender's e-mail address). - `PASSWD`: **_empty_**: Password of mailing user. Use \`your password\` for quoting if you use special characters in the password. - - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](administration/email-setup.md) for more information. + - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](../administration/email-setup.md) for more information. - `ENABLE_HELO`: **true**: Enable HELO operation. - `HELO_HOSTNAME`: **(retrieved from system)**: HELO hostname. - `FROM`: **_empty_**: Mail from address, RFC 5322. This can be just an email address, or the "Name" \ format. diff --git a/versioned_docs/version-1.22/administration/customizing-gitea.md b/versioned_docs/version-1.22/administration/customizing-gitea.md index 4af254f8..d364c403 100644 --- a/versioned_docs/version-1.22/administration/customizing-gitea.md +++ b/versioned_docs/version-1.22/administration/customizing-gitea.md @@ -36,7 +36,7 @@ Application settings can be found in file `CustomConf` which is by default, Again `gitea help` will allow you review this variable and you can override it using the `--config` option on the `gitea` binary. -- [Quick Cheat Sheet](administration/config-cheat-sheet.md) +- [Quick Cheat Sheet](../administration/config-cheat-sheet.md) - [Complete List](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini) If the `CustomPath` folder can't be found despite checking `gitea help`, check the `GITEA_CUSTOM` @@ -44,7 +44,7 @@ environment variable; this can be used to override the default path to something `GITEA_CUSTOM` might, for example, be set by an init script. You can check whether the value is set under the "Configuration" tab on the site administration page. -- [List of Environment Variables](administration/environment-variables.md) +- [List of Environment Variables](../administration/environment-variables.md) :::note Gitea must perform a full restart to see configuration changes. @@ -89,7 +89,7 @@ directory at the top of this document). Every single page of Gitea can be changed. Dynamic content is generated using [go templates](https://pkg.go.dev/html/template), which can be modified by placing replacements below the `$GITEA_CUSTOM/templates` directory. -To obtain any embedded file (including templates), the [`gitea embedded` tool](administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using). +To obtain any embedded file (including templates), the [`gitea embedded` tool](../administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using). Be aware that any statement contained inside `{{` and `}}` are Gitea's template syntax and shouldn't be touched without fully understanding these components. @@ -110,7 +110,7 @@ just place it under your "$GITEA_CUSTOM/public/assets/" directory (for instance To match the current style, the link should have the class name "item", and you can use `{{AppSubUrl}}` to get the base URL: `Impressum` -For more information, see [Adding Legal Pages](administration/adding-legal-pages.md). +For more information, see [Adding Legal Pages](../administration/adding-legal-pages.md). You can add new tabs in the same way, putting them in `extra_tabs.tmpl`. The exact HTML needed to match the style of other tabs is in the file @@ -378,10 +378,10 @@ A full list of supported emoji's is at [emoji list](https://gitea.com/gitea/gite The built-in themes are `gitea-light`, `gitea-dark`, and `gitea-auto` (which automatically adapts to OS settings). -The default theme can be changed via `DEFAULT_THEME` in the [ui](administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. +The default theme can be changed via `DEFAULT_THEME` in the [ui](../administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. Gitea also has support for user themes, which means every user can select which theme should be used. -The list of themes a user can choose from can be configured with the `THEMES` value in the [ui](administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. +The list of themes a user can choose from can be configured with the `THEMES` value in the [ui](../administration/config-cheat-sheet.md#ui-ui) section of `app.ini`. To make a custom theme available to all users: diff --git a/versioned_docs/version-1.22/administration/email-setup.md b/versioned_docs/version-1.22/administration/email-setup.md index 690d8041..1c8b3b99 100644 --- a/versioned_docs/version-1.22/administration/email-setup.md +++ b/versioned_docs/version-1.22/administration/email-setup.md @@ -55,7 +55,7 @@ Restart Gitea for the configuration changes to take effect. To send a test email to validate the settings, go to Gitea > Site Administration > Configuration > SMTP Mailer Configuration. -For the full list of options check the [Config Cheat Sheet](administration/config-cheat-sheet.md) +For the full list of options check the [Config Cheat Sheet](../administration/config-cheat-sheet.md) Please note: authentication is only supported when the SMTP server communication is encrypted with TLS or `HOST=localhost`. TLS encryption can be through: diff --git a/versioned_docs/version-1.22/administration/external-renderers.md b/versioned_docs/version-1.22/administration/external-renderers.md index fec2ab64..8ab1b8d8 100644 --- a/versioned_docs/version-1.22/administration/external-renderers.md +++ b/versioned_docs/version-1.22/administration/external-renderers.md @@ -24,7 +24,7 @@ it is just a matter of: - add some configuration to your `app.ini` file - restart your Gitea instance -This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](administration/customizing-gitea.md) page. +This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](../administration/customizing-gitea.md) page. ## Installing external binaries diff --git a/versioned_docs/version-1.22/administration/fail2ban-setup.md b/versioned_docs/version-1.22/administration/fail2ban-setup.md index c90f88c8..0f5ac77b 100644 --- a/versioned_docs/version-1.22/administration/fail2ban-setup.md +++ b/versioned_docs/version-1.22/administration/fail2ban-setup.md @@ -119,7 +119,7 @@ proxy_set_header X-Real-IP $remote_addr; The security options in `app.ini` need to be adjusted to allow the interpretation of the headers as well as the list of IP addresses and networks that describe trusted proxy servers -(See the [configuration cheat sheet](administration/config-cheat-sheet.md#security-security) for more information). +(See the [configuration cheat sheet](../administration/config-cheat-sheet.md#security-security) for more information). ``` REVERSE_PROXY_LIMIT = 1 diff --git a/versioned_docs/version-1.22/administration/https-support.md b/versioned_docs/version-1.22/administration/https-support.md index 981a29bd..8adb2987 100644 --- a/versioned_docs/version-1.22/administration/https-support.md +++ b/versioned_docs/version-1.22/administration/https-support.md @@ -22,7 +22,7 @@ menu: Before you enable HTTPS, make sure that you have valid SSL/TLS certificates. You could use self-generated certificates for evaluation and testing. Please run `gitea cert --host [HOST]` to generate a self signed certificate. -If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](administration/reverse-proxies.md). +If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](../administration/reverse-proxies.md). To use Gitea's built-in HTTPS support, you must change your `app.ini` file: @@ -36,7 +36,7 @@ KEY_FILE = key.pem ``` Note that if your certificate is signed by a third party certificate authority (i.e. not self-signed), then cert.pem should contain the certificate chain. The server certificate must be the first entry in cert.pem, followed by the intermediaries in order (if any). The root certificate does not have to be included because the connecting client must already have it in order to establish the trust relationship. -To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](../administration/config-cheat-sheet.md#server-server). For the `CERT_FILE` or `KEY_FILE` field, the file path is relative to the `GITEA_CUSTOM` environment variable when it is a relative path. It can be an absolute path as well. @@ -85,11 +85,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](../administration/config-cheat-sheet.md#server-server). ## Using a reverse proxy -Setup up your reverse proxy as shown in the [reverse proxy guide](administration/reverse-proxies.md). +Setup up your reverse proxy as shown in the [reverse proxy guide](../administration/reverse-proxies.md). After that, enable HTTPS by following one of these guides: diff --git a/versioned_docs/version-1.22/administration/mail-templates.md b/versioned_docs/version-1.22/administration/mail-templates.md index 8e4e416e..1edbd677 100644 --- a/versioned_docs/version-1.22/administration/mail-templates.md +++ b/versioned_docs/version-1.22/administration/mail-templates.md @@ -18,7 +18,7 @@ menu: # Mail templates To craft the e-mail subject and contents for certain operations, Gitea can be customized by using templates. The templates -for these functions are located under the [`custom` directory](administration/customizing-gitea.md). +for these functions are located under the [`custom` directory](../administration/customizing-gitea.md). Gitea has an internal template that serves as default in case there's no custom alternative. Custom templates are loaded when Gitea starts. Changes made to them are not recognized until Gitea is restarted again. @@ -165,7 +165,7 @@ If the template fails to render, it will be noticed only at the moment the mail A default subject is used if the subject template fails, and whatever was rendered successfully from the _mail body_ is used, disregarding the rest. -Please check [Gitea's logs](administration/logging-config.md) for error messages in case of trouble. +Please check [Gitea's logs](../administration/logging-config.md) for error messages in case of trouble. ## Example diff --git a/versioned_docs/version-1.22/administration/repo-indexer.md b/versioned_docs/version-1.22/administration/repo-indexer.md index aa822229..be37a8a1 100644 --- a/versioned_docs/version-1.22/administration/repo-indexer.md +++ b/versioned_docs/version-1.22/administration/repo-indexer.md @@ -25,7 +25,7 @@ Better code search support could be achieved by setting up the repository indexe ## Setting up the repository indexer -Gitea can search through the files of the repositories by enabling this function in your [`app.ini`](administration/config-cheat-sheet.md): +Gitea can search through the files of the repositories by enabling this function in your [`app.ini`](../administration/config-cheat-sheet.md): ```ini [indexer] diff --git a/versioned_docs/version-1.22/administration/search-engines-indexation.md b/versioned_docs/version-1.22/administration/search-engines-indexation.md index 66494069..0140d68a 100644 --- a/versioned_docs/version-1.22/administration/search-engines-indexation.md +++ b/versioned_docs/version-1.22/administration/search-engines-indexation.md @@ -23,7 +23,7 @@ If you don't want your repository to be visible for search engines read further. ## Block search engines indexation using robots.txt To make Gitea serve a custom `robots.txt` (default: empty 404) for top level installations, -create a file with path `public/robots.txt` in the [`custom` folder or `CustomPath`](administration/customizing-gitea.md) +create a file with path `public/robots.txt` in the [`custom` folder or `CustomPath`](../administration/customizing-gitea.md) Examples on how to configure the `robots.txt` can be found at [https://moz.com/learn/seo/robotstxt](https://moz.com/learn/seo/robotstxt). diff --git a/versioned_docs/version-1.22/development/api-usage.md b/versioned_docs/version-1.22/development/api-usage.md index 4fe376b1..59a31d1e 100644 --- a/versioned_docs/version-1.22/development/api-usage.md +++ b/versioned_docs/version-1.22/development/api-usage.md @@ -19,7 +19,7 @@ menu: ## Enabling/configuring API access -By default, `ENABLE_SWAGGER` is true, and `MAX_RESPONSE_ITEMS` is set to 50. See [Config Cheat Sheet](administration/config-cheat-sheet.md) for more information. +By default, `ENABLE_SWAGGER` is true, and `MAX_RESPONSE_ITEMS` is set to 50. See [Config Cheat Sheet](../administration/config-cheat-sheet.md) for more information. ## Authentication diff --git a/versioned_docs/version-1.22/development/hacking-on-gitea.md b/versioned_docs/version-1.22/development/hacking-on-gitea.md index eba4da17..e7fceb87 100644 --- a/versioned_docs/version-1.22/development/hacking-on-gitea.md +++ b/versioned_docs/version-1.22/development/hacking-on-gitea.md @@ -271,7 +271,7 @@ Please note you should use the Swagger 2.0 documentation, not the OpenAPI 3 docu When creating new configuration options, it is not enough to add them to the `modules/setting` files. You should add information to `custom/conf/app.ini` and to the -[configuration cheat sheet](administration/config-cheat-sheet.md) +[configuration cheat sheet](../administration/config-cheat-sheet.md) found in `docs/content/doc/administer/config-cheat-sheet.en-us.md` ### Changing the logo diff --git a/versioned_docs/version-1.22/help/faq.md b/versioned_docs/version-1.22/help/faq.md index 7ffeb2a2..1555684e 100644 --- a/versioned_docs/version-1.22/help/faq.md +++ b/versioned_docs/version-1.22/help/faq.md @@ -86,7 +86,7 @@ https://github.com/loganinak/MigrateGitlabToGogs There are a few places that could make this show incorrectly. -1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](administration/reverse-proxies.md) +1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](../administration/reverse-proxies.md) 2. Make sure you have correctly set `ROOT_URL` in the `server` section of your `app.ini` If certain clone options aren't showing up (HTTP/S or SSH), the following options can be checked in your `app.ini` @@ -99,7 +99,7 @@ If certain clone options aren't showing up (HTTP/S or SSH), the following option This error occurs when the reverse proxy limits the file upload size. -See the [reverse proxy guide](administration/reverse-proxies.md) for a solution with nginx. +See the [reverse proxy guide](../administration/reverse-proxies.md) for a solution with nginx. ## Custom Templates not loading or working incorrectly @@ -109,7 +109,7 @@ The correct path for the template(s) will be relative to the `CustomPath` 1. To find `CustomPath`, look for Custom File Root Path in Site Administration -> Configuration 2. If you are still unable to find a path, the default can be [calculated above](#where-does-gitea-store-what-file) -3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](administration/customizing-gitea.md) page to add your template to the correct location. +3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](../administration/customizing-gitea.md) page to add your template to the correct location. ## Does Gitea have a "GitHub/GitLab pages" feature? @@ -127,7 +127,7 @@ A "login prohibited" user is a user that is not allowed to log in to Gitea anymo ## Setting up logging -- [Official Docs](administration/logging-config.md) +- [Official Docs](../administration/logging-config.md) ## What is Swagger? @@ -150,7 +150,7 @@ There are multiple things you can combine to prevent spammers. 1. By whitelisting or blocklisting certain email domains 2. By only whitelisting certain domains with OpenID (see below) 3. Setting `ENABLE_CAPTCHA` to `true` in your `app.ini` and properly configuring `RECAPTCHA_SECRET` and `RECAPTCHA_SITEKEY` -4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI +4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](../administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI ### Only allow/block certain email domains @@ -178,7 +178,7 @@ At some point, a customer or third party needs access to a specific repo and onl ### Enable Fail2ban -Use [Fail2Ban](administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns +Use [Fail2Ban](../administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns ## SSHD vs built-in SSH @@ -322,24 +322,24 @@ You may want to set this value to `60m` or `120m`. ## How can I create users before starting Gitea -Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](administration/command-line.md#admin) to add users like normal. +Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](../administration/command-line.md#admin) to add users like normal. ## How can I enable password reset -There is no setting for password resets. It is enabled when a [mail service](administration/email-setup.md) is configured, and disabled otherwise. +There is no setting for password resets. It is enabled when a [mail service](../administration/email-setup.md) is configured, and disabled otherwise. ## How can a user's password be changed - As an **admin**, you can change any user's password (and optionally force them to change it on next login)... - By navigating to your `Site Administration -> User Accounts` page and editing a user. - - By using the [admin CLI commands](administration/command-line.md#admin). + - By using the [admin CLI commands](../administration/command-line.md#admin). - Keep in mind most commands will also need a [global flag](administration/command-line.md#global-options) to point the CLI at the correct configuration. + Keep in mind most commands will also need a [global flag](../administration/command-line.md#global-options) to point the CLI at the correct configuration. - As a **user** you can change it... - In your account `Settings -> Account` page (this method **requires** you to know your current password). - By using the `Forgot Password` link. - If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](administration/email-setup.md). + If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](../administration/email-setup.md). ## Why is my markdown broken @@ -417,9 +417,9 @@ It is highly recommended to back-up your database before running these commands. - You can also check `/admin/config` for the repository root path. - Ensure that the user/org exists that you want to adopt repositories for. - As an admin, go to `/admin/repos/unadopted` and search. - - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository). + - Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](../administration/config-cheat-sheet.md#repository-repository). - If the above steps are done correctly, you should be able to select repositories to adopt. - - If no repositories are found, enable [debug logging](administration/config-cheat-sheet.md#repository) to check for any specific errors. + - If no repositories are found, enable [debug logging](../administration/config-cheat-sheet.md#repository-repository) to check for any specific errors. ## Gitea can't start on NFS diff --git a/versioned_docs/version-1.22/index.md b/versioned_docs/version-1.22/index.md index 73dc86d6..f2f3752c 100644 --- a/versioned_docs/version-1.22/index.md +++ b/versioned_docs/version-1.22/index.md @@ -15,7 +15,7 @@ blog post to read about the justification for a fork. :::warning -Gitea has never sent commits to upstream or cherry-pick commits from upstream. So Gitea is totally not compatible with Gogs. No any gurantee it can work if you upgrade from Gogs to Gitea. The recommands method is to migrate repositories from Gogs to Gitea. +Gitea has never sent commits to upstream or cherry-pick commits from upstream. So Gitea is totally not compatible with Gogs. No any gurantee it can work if you upgrade from Gogs to Gitea. The recommanded method is to migrate repositories from Gogs to Gitea. ::: diff --git a/versioned_docs/version-1.22/installation/comparison.md b/versioned_docs/version-1.22/installation/comparison.md index 3fb6561f..18ef6f94 100644 --- a/versioned_docs/version-1.22/installation/comparison.md +++ b/versioned_docs/version-1.22/installation/comparison.md @@ -88,7 +88,7 @@ _Symbols used in table:_ | Visual comparison of image changes | ✓ | ✘ | ✓ | ? | ? | ? | ✘ | ✘ | - Gitea has builtin repository-level code search -- Better code search support could be achieved by [using a repository indexer](administration/repo-indexer.md) +- Better code search support could be achieved by [using a repository indexer](../administration/repo-indexer.md) ## Issue Tracker diff --git a/versioned_docs/version-1.22/installation/from-binary.md b/versioned_docs/version-1.22/installation/from-binary.md index 4688d699..c5887c60 100644 --- a/versioned_docs/version-1.22/installation/from-binary.md +++ b/versioned_docs/version-1.22/installation/from-binary.md @@ -63,7 +63,7 @@ despite warnings like `This key is not certified with a trusted signature!`. ## Recommended server configuration :::note -Many of the following directories can be configured using [Environment Variables](administration/environment-variables.md) as well! +Many of the following directories can be configured using [Environment Variables](../administration/environment-variables.md) as well! Of note, configuring `GITEA_WORK_DIR` will tell Gitea where to base its working directory, as well as ease installation. ::: @@ -127,7 +127,7 @@ If you don't want the web installer to be able to write to the config file, it i * Ensure that the `SECRET_KEY` and `INTERNAL_TOKEN` values are set. (You may want to use the `gitea generate secret` to generate these secret keys.) * Ensure that any other secret keys you need are set. -See the [command line documentation](administration/command-line.md) for information on using `gitea generate secret`. +See the [command line documentation](../administration/command-line.md) for information on using `gitea generate secret`. ### Configure Gitea's working directory @@ -174,7 +174,7 @@ GITEA_WORK_DIR=/var/lib/gitea/ /usr/local/bin/gitea web -c /etc/gitea/app.ini You can update to a new version of Gitea by stopping Gitea, replacing the binary at `/usr/local/bin/gitea` and restarting the instance. The binary file name should not be changed during the update to avoid problems in existing repositories. -It is recommended that you make a [backup](administration/backup-and-restore.md) before updating your installation. +It is recommended that you make a [backup](../administration/backup-and-restore.md) before updating your installation. If you have carried out the installation steps as described above, the binary should have the generic name `gitea`. Do not change this, i.e. to include the version number. diff --git a/versioned_docs/version-1.22/installation/with-docker-rootless.md b/versioned_docs/version-1.22/installation/with-docker-rootless.md index df287c55..ddd5d8e0 100644 --- a/versioned_docs/version-1.22/installation/with-docker-rootless.md +++ b/versioned_docs/version-1.22/installation/with-docker-rootless.md @@ -256,7 +256,7 @@ documented above, please note that `db` must be used as the database hostname. ## Customization -Customization files described [here](administration/customizing-gitea.md) should +Customization files described [here](../administration/customizing-gitea.md) should be placed in `/var/lib/gitea/custom` directory. If using host volumes, it's quite easy to access these files; for named volumes, this is done through another container or by direct access at `/var/lib/docker/volumes/gitea_gitea/_/var_lib_gitea`. The configuration file will be saved at @@ -317,7 +317,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -To set required TOKEN and SECRET values, consider using Gitea's built-in [generate utility functions](administration/command-line.md#generate). +To set required TOKEN and SECRET values, consider using Gitea's built-in [generate utility functions](../administration/command-line.md#generate). # SSH Container Passthrough @@ -346,7 +346,7 @@ Once the wrapper is in place, you can make it the shell for the `git` user: sudo usermod -s /usr/local/bin/gitea-shell git ``` -Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the [SSH AuthorizedKeysCommand](administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: +Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: ```bash Match User git diff --git a/versioned_docs/version-1.22/installation/with-docker.md b/versioned_docs/version-1.22/installation/with-docker.md index 6102d7d7..5e682b75 100644 --- a/versioned_docs/version-1.22/installation/with-docker.md +++ b/versioned_docs/version-1.22/installation/with-docker.md @@ -263,7 +263,7 @@ documented above, please note that `db` must be used as the database hostname. ## Customization -Customization files described [here](administration/customizing-gitea.md) should +Customization files described [here](../administration/customizing-gitea.md) should be placed in `/data/gitea` directory. If using host volumes, it's quite easy to access these files; for named volumes, this is done through another container or by direct access at `/var/lib/docker/volumes/gitea_gitea/_data`. The configuration file will be saved at @@ -314,7 +314,7 @@ services: - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}""" ``` -Gitea will generate new secrets/tokens for every new installation automatically and write them into the app.ini. If you want to set the secrets/tokens manually, you can use the following docker commands to use of Gitea's built-in [generate utility functions](administration/command-line.md#generate). Do not lose/change your SECRET_KEY after the installation, otherwise the encrypted data can not be decrypted anymore. +Gitea will generate new secrets/tokens for every new installation automatically and write them into the app.ini. If you want to set the secrets/tokens manually, you can use the following docker commands to use of Gitea's built-in [generate utility functions](../administration/command-line.md#generate). Do not lose/change your SECRET_KEY after the installation, otherwise the encrypted data can not be decrypted anymore. The following commands will output a new `SECRET_KEY` and `INTERNAL_TOKEN` to `stdout`, which you can then place in your environment variables. @@ -558,7 +558,7 @@ In this option, the idea is that the host SSH uses an `AuthorizedKeysCommand` in Now all attempts to login as the `git` user on the host will be forwarded to the docker - including the `SSH_ORIGINAL_COMMAND`. We now need to set-up SSH authentication on the host. -We will do this by leveraging the [SSH AuthorizedKeysCommand](administration/command-line.md#keys) to match the keys against those accepted by Gitea. +We will do this by leveraging the [SSH AuthorizedKeysCommand](../administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host: diff --git a/versioned_docs/version-1.22/search.md b/versioned_docs/version-1.22/search.md deleted file mode 100644 index 226d9fe3..00000000 --- a/versioned_docs/version-1.22/search.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -date: "2019-11-12T16:00:00+02:00" -title: "Search" -slug: "search" -sidebar_position: 1 -toc: false -draft: false -aliases: - - /en-us/help/search -sitemap: - priority : 1 -layout: "search" ---- - -This file exists solely to respond to /search URL with the related `search` layout template. - -No content shown here is rendered, all content is based in the template layouts/doc/search.html - -Setting a very low sitemap priority will tell search engines this is not important content. diff --git a/versioned_docs/version-1.22/usage/actions/act-runner.md b/versioned_docs/version-1.22/usage/actions/act-runner.md index 942d1269..c51e920b 100644 --- a/versioned_docs/version-1.22/usage/actions/act-runner.md +++ b/versioned_docs/version-1.22/usage/actions/act-runner.md @@ -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.md#actions-generate-runner-token): +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 diff --git a/versioned_docs/version-1.22/usage/actions/comparison.md b/versioned_docs/version-1.22/usage/actions/comparison.md index 5b084e09..4af66960 100644 --- a/versioned_docs/version-1.22/usage/actions/comparison.md +++ b/versioned_docs/version-1.22/usage/actions/comparison.md @@ -136,7 +136,7 @@ If you want to download an action from another git hoster, you can use an absolu If your Gitea instance is in an intranet or a restricted area, you can set the URL to `self` to only download actions from your own instance by default. Of course, you can still use absolute URLs in workflows. -More details about the `[actions].DEFAULT_ACTIONS_URL` configuration can be found in the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions)。 +More details about the `[actions].DEFAULT_ACTIONS_URL` configuration can be found in the [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions)。 ### Context availability diff --git a/versioned_docs/version-1.22/usage/actions/faq.md b/versioned_docs/version-1.22/usage/actions/faq.md index 74eb0654..7d4804cc 100644 --- a/versioned_docs/version-1.22/usage/actions/faq.md +++ b/versioned_docs/version-1.22/usage/actions/faq.md @@ -62,7 +62,7 @@ This is one of the differences from GitHub Actions which supports actions script But it should allow users much more flexibility in how they run Actions. Alternatively, if you want your runners to download actions from your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`. -See [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions). +See [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions). ## How to limit the permission of the runners? diff --git a/versioned_docs/version-1.22/usage/actions/quickstart.md b/versioned_docs/version-1.22/usage/actions/quickstart.md index 0514b6dd..e6e3a503 100644 --- a/versioned_docs/version-1.22/usage/actions/quickstart.md +++ b/versioned_docs/version-1.22/usage/actions/quickstart.md @@ -30,7 +30,7 @@ Since 1.21.0, Actions are enabled by default. If you are using versions before 1 ENABLED=true ``` -If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions). +If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet](../../administration/config-cheat-sheet.md#actions-actions). ### Set up runner @@ -129,7 +129,7 @@ That is because Gitea Actions is designed to be compatible with GitHub Actions Be careful, the demo file contains some emojis. Please make sure your database supports them, especially when using MySQL. If the charset is not `utf8mb4`, errors will occur, such as `Error 1366 (HY000): Incorrect string value: '\\xF0\\x9F\\x8E\\x89 T...' for column 'name' at row 1`. -See [Database Preparation](installation/database-preparation.md#mysql) for more information. +See [Database Preparation](../../installation/database-preparation.md#mysqlmariadb) for more information. Alternatively, you can remove all emojis from the demo file and try again. diff --git a/versioned_docs/version-1.22/usage/linked-references.md b/versioned_docs/version-1.22/usage/linked-references.md index a0acb024..b6f733dd 100644 --- a/versioned_docs/version-1.22/usage/linked-references.md +++ b/versioned_docs/version-1.22/usage/linked-references.md @@ -94,7 +94,7 @@ Sometimes a commit or pull request may fix or bring back a problem documented in a particular issue. Gitea supports closing and reopening the referenced issues by preceding the reference with a particular _keyword_. Common keywords include "closes", "fixes", "reopens", etc. This list can be -[customized](administration/config-cheat-sheet.md) by the +[customized](../administration/config-cheat-sheet.md) by the site administrator. Example: diff --git a/versioned_docs/version-1.22/usage/packages/storage.md b/versioned_docs/version-1.22/usage/packages/storage.md index f437412d..3db44aaa 100644 --- a/versioned_docs/version-1.22/usage/packages/storage.md +++ b/versioned_docs/version-1.22/usage/packages/storage.md @@ -28,7 +28,7 @@ Whenever a package gets deleted, only the references to the underlying blobs are The blobs get not removed at this moment, so they still require space on the filesystem. When a new package gets uploaded the existing blobs may get referenced again. -These unreferenced blobs get deleted by a [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages). +These unreferenced blobs get deleted by a [clean up job](../../administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages). The config setting `OLDER_THAN` configures how long unreferenced blobs are kept before they get deleted. ## Cleanup Rules @@ -68,7 +68,7 @@ The patterns are case-insensitive which matches the behaviour of the package reg ### How the cleanup rules work -The cleanup rules are part of the [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically. +The cleanup rules are part of the [clean up job](../../administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically. The cleanup rule: diff --git a/versioned_docs/version-1.22/usage/push.md b/versioned_docs/version-1.22/usage/push.md index d88dc1a2..a8c87a46 100644 --- a/versioned_docs/version-1.22/usage/push.md +++ b/versioned_docs/version-1.22/usage/push.md @@ -51,7 +51,7 @@ Push to create is a feature that allows you to push to a repository that does no ## Enabling Push To Create -In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#repository-repository). +In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](../administration/config-cheat-sheet.md#repository-repository). ## Using Push To Create