diff options
author | silverwind <me@silverwind.io> | 2020-02-22 10:15:11 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-02-22 17:15:11 +0800 |
commit | 2ed9ead6dea29f9e006fa1831892c9c239f4bd70 (patch) | |
tree | c267fc66212a0ebce2a6f0b38ce8537c43903b14 /docs | |
parent | c8d1c3812980573eae0a1ecd5e84c8b44457c3e4 (diff) | |
download | gitea-2ed9ead6dea29f9e006fa1831892c9c239f4bd70.tar.gz gitea-2ed9ead6dea29f9e006fa1831892c9c239f4bd70.zip |
Add frontend/backend make targets, fix source release (#10325)
* Add frontend/backend make targets, fix source release
- Add 'make backend' and 'make frontend' make targets which are used to
build go and js/css/svg files respectively.
- The 'backend' target can be invoked without requiring Node.js to be
present on the system if pre-built frontend assets are present like
in the release source tarballs.
- Fix source releases missing 'dist' folders inside 'node_modules' which
were erronously excluded from tar.
- Store VERSION in file VERSION for the release tarballs and prefer that
file over git-derived version.
* fix release task
* fix typo
* fix another typo
Diffstat (limited to 'docs')
-rw-r--r-- | docs/content/doc/installation/from-source.en-us.md | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/content/doc/installation/from-source.en-us.md b/docs/content/doc/installation/from-source.en-us.md index fcd6fae166..cb98484221 100644 --- a/docs/content/doc/installation/from-source.en-us.md +++ b/docs/content/doc/installation/from-source.en-us.md @@ -114,6 +114,17 @@ recommended way to build from source is therefore: TAGS="bindata sqlite sqlite_unlock_notify" make build ``` +The `build` target is split into two sub-targets: + +- `make backend` which requires [Go 1.11](https://golang.org/dl/) or greater. +- `make frontend` which requires [Node.js 10.0.0](https://nodejs.org/en/download/) or greater. + +If pre-built frontend files are present it is possible to only build the backend: + +```bash +TAGS="bindata" make backend +`` + ## Test After following the steps above, a `gitea` binary will be available in the working directory. |