Fix "build from source" document to clarify the bindata
tag is required.
#21853
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related: #21845
I have seen many users not using
bindata
and asking "why my Gitea build doesn't work".For almost 100% users, the
bindata
tag is required for the production build, thebindata
contains not only the JS/CSS files, but also other essential backend data like templates.Without
bindata
, Gitea is unlikely to run correctly in a production deployment.If some advanced users want to fine tune the build, they should look into source code and other documents to separate bindata files carefully and manually.