recommend bindata for building (#11938)
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
This commit is contained in:
parent
654a970644
commit
4d2c2962d3
1 changed files with 4 additions and 2 deletions
|
@ -98,8 +98,10 @@ Depending on requirements, the following build tags can be included.
|
||||||
be used to authenticate local users or extend authentication to methods
|
be used to authenticate local users or extend authentication to methods
|
||||||
available to PAM.
|
available to PAM.
|
||||||
|
|
||||||
Bundling assets into the binary using the `bindata` build tag can make
|
Bundling assets into the binary using the `bindata` build tag is recommended for
|
||||||
development and testing easier, but is not ideal for a production deployment.
|
production deployments. It is possible to serve the static assets directly via a reverse proxy,
|
||||||
|
but in most cases it is not necessary, and assets should still be bundled in the binary.
|
||||||
|
You may want to exclude bindata while developing/testing Gitea.
|
||||||
To include assets, add the `bindata` tag:
|
To include assets, add the `bindata` tag:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
|
|
Reference in a new issue