lavender-legacy
/
gitea
7
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Use correct make target for building static assets (#12247) 

The webpack make target does not build semantic-ui
release/v1.15
Ben Harris 2020-07-14 15:45:23 -04:00 committed by GitHub
parent 3b498ebc77
commit a4da46d182
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/content/doc/usage/reverse-proxies.en-us.md
View File

@ -55,7 +55,7 @@ Nginx is optimized for serving static content, while the proxying of large respo
(see https://serverfault.com/q/587386). (see https://serverfault.com/q/587386).
Download a snapshot of the Gitea source repository to `/path/to/gitea/`. 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) (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, Depending on the scale of your user base, you might want to split the traffic to two distinct servers,