From a4da46d182c244a8d61de089d0400128924d847c Mon Sep 17 00:00:00 2001 From: Ben Harris <ben@tilde.team> Date: Tue, 14 Jul 2020 15:45:23 -0400 Subject: [PATCH] Use correct make target for building static assets (#12247) The webpack make target does not build semantic-ui --- 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 c31576ecb8..ac980a6ee5 100644 --- a/docs/content/doc/usage/reverse-proxies.en-us.md +++ b/docs/content/doc/usage/reverse-proxies.en-us.md @@ -55,7 +55,7 @@ Nginx is optimized for serving static content, while the proxying of large respo (see https://serverfault.com/q/587386). Download a snapshot of the Gitea source repository to `/path/to/gitea/`. -After this, run `make webpack` 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. +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. (You will need to have [Node with npm](https://nodejs.org/en/download/) and `make` installed to generate the static resources) Depending on the scale of your user base, you might want to split the traffic to two distinct servers,