From 4d2c2962d36aec08a8aa8c849db7336a08052741 Mon Sep 17 00:00:00 2001 From: techknowlogick Date: Thu, 18 Jun 2020 11:25:58 -0400 Subject: [PATCH] recommend bindata for building (#11938) Co-authored-by: John Olheiser --- docs/content/doc/installation/from-source.en-us.md | 6 ++++-- 1 file 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 d70e00035..cf3f599c5 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