aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/doc/installation/from-source.en-us.md
diff options
context:
space:
mode:
authortechknowlogick <techknowlogick@gitea.io>2020-06-18 11:25:58 -0400
committerGitHub <noreply@github.com>2020-06-18 11:25:58 -0400
commit4d2c2962d36aec08a8aa8c849db7336a08052741 (patch)
tree76a3a5a72278079248d6d654e04be1e1036deb94 /docs/content/doc/installation/from-source.en-us.md
parent654a97064495213531efdfc2571f659b45236633 (diff)
downloadgitea-4d2c2962d36aec08a8aa8c849db7336a08052741.tar.gz
gitea-4d2c2962d36aec08a8aa8c849db7336a08052741.zip
recommend bindata for building (#11938)
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
Diffstat (limited to 'docs/content/doc/installation/from-source.en-us.md')
-rw-r--r--docs/content/doc/installation/from-source.en-us.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/content/doc/installation/from-source.en-us.md b/docs/content/doc/installation/from-source.en-us.md
index d70e000352..cf3f599c56 100644
--- a/docs/content/doc/installation/from-source.en-us.md
+++ b/docs/content/doc/installation/from-source.en-us.md
@@ -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
available to PAM.
-Bundling assets into the binary using the `bindata` build tag can make
-development and testing easier, but is not ideal for a production deployment.
+Bundling assets into the binary using the `bindata` build tag is recommended for
+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:
```bash