| commit | 7cadbc0c0c64b47204cf0de293b7c68814774652 | [log] [tgz] |
|---|---|---|
| author | Dave Borowitz <dborowitz@google.com> | Wed Nov 04 12:14:12 2015 -0500 |
| committer | Dave Borowitz <dborowitz@google.com> | Thu Nov 12 18:39:59 2015 -0500 |
| tree | 855ac89aa79c8092a7d6328893c8cba1884099a0 | |
| parent | 2baf2985c4f5456fa9cf3fb61561466b40e49b44 [diff] |
Serve PolyGerrit static paths PolyGerrit is a purely static web app. This means all UI-related endpoints just serve static content. In the developer case, the mapping looks like: / => polygerrit-ui/app/index.html /bower_components/* => polygerrit-ui/bower_components/* /* => polygerrit-ui/app/* In addition, PolyGerrit uses the HTML5 history API, which among other things replaces fragments used by GWT (#/c/1234) with actual paths (/c/1234). This means all paths formerly dispatched in Dispatcher.java have to be served as app/index.html, except for a few that are currently overlapping with the REST API (/projects and /groups/). We are still using PolyGerrit's native build system, which means the build steps in README.md need to be run on setup and any time dependencies change. This is the step that is responsible for setting up polygerrit-ui/bower_components/. In the compiled WAR case, lots of minification and inlining happens, so we just need to serve static content out of /polygerrit_ui/* in the WAR file. Note that WAR file integration is not implemented yet, since a) we need to tweak the buck build to allow this, and b) we need to do license auditing before inlining a bunch of code into the UI. Change-Id: I9d000f6fa1ae75e966593c174f43c9f366f7dcff
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Buck and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit
cd gerrit && buck build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.