From 4d22e2423ffbf3067349c8d0fad4967e5f6b9706 Mon Sep 17 00:00:00 2001 From: Donlon Date: Tue, 22 Dec 2020 23:54:12 +0800 Subject: [PATCH] Fix incorrect generated link in documentation page (#14112) --- docs/content/doc/usage/reverse-proxies.en-us.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/doc/usage/reverse-proxies.en-us.md b/docs/content/doc/usage/reverse-proxies.en-us.md index 714e912d8..74e39039d 100644 --- a/docs/content/doc/usage/reverse-proxies.en-us.md +++ b/docs/content/doc/usage/reverse-proxies.en-us.md @@ -60,7 +60,7 @@ The front page, a repository view or issue list is dynamic content. Nginx can serve static resources directly and proxy only the dynamic requests to gitea. Nginx is optimized for serving static content, while the proxying of large responses might be the opposite of that -(see https://serverfault.com/q/587386). +(see [https://serverfault.com/q/587386](https://serverfault.com/q/587386)). Download a snapshot of the Gitea source repository to `/path/to/gitea/`. After this, run `make frontend` in the repository directory to generate the static resources. We are only interested in the `public/` directory for this task, so you can delete the rest.