| commit | ed3c2d11fc470e317df9c9fc9f61cba64f77a221 | [log] [tgz] |
|---|---|---|
| author | Shawn Pearce <sop@google.com> | Mon May 30 15:59:02 2016 -0700 |
| committer | Shawn Pearce <sop@google.com> | Mon May 30 15:59:05 2016 -0700 |
| tree | c7a7f73a76ca0e61aa44e6bfd0d1c82f76a2ba34 | |
| parent | 3c0207e9efc488c9365d707ec13dad6cd8ca9fc4 [diff] |
Include Vary: Accept-Encoding when using gzip This is strongly encouraged to ensure caches only send a cached gzip response only to user agents that understand gzip encoding. Gitiles has been getting lucky due to most responses being uncached, or cached only on the end user's browser with ETag revalidation. We may in the future want to allow caching public resources that are anonymously available. Doing this fix now ensures we are not surprised later if we try to improve the HTTP caching headers. Change-Id: Ide66426c956813218d10bdad99af775ca6a5e2be
Gitiles is a simple repository browser for Git repositories, built on JGit. Its guiding principle is simplicity: it has no formal access controls, no write access, no fancy Javascript, etc.
Gitiles requires Buck to build.
sudo apt-get install ant
cd ${HOME}
git clone https://github.com/facebook/buck.git
cd buck
ant
sudo ln -s ${PWD}/bin/buck /usr/bin/buck
cd /path/to/gitiles
git submodule update --init
buck build all
buck test
cd /path/to/repositories # Don't run from the gitiles repo. /path/to/gitiles/tools/run_dev.sh
This will recompile and start a development server. Open http://localhost:8080/ to view your local copy of gitiles, which will serve any repositories under /path/to/repositories.
To run unit tests, run buck test.
If you'd like to use Eclipse to edit Gitiles, first generate a project file:
./bucklets/tools/eclipse.py --src
Import the project in Eclipse:
File -> Import -> Existing Projects into Workpace
The project only needs to be rebuilt if the source roots or third-party libraries have changed. For best results, ensure the project is closed in Eclipse before rebuilding.
Java code in Gitiles follows the Google Java Style Guide with a 100-column limit.
Code should be automatically formatted using google-java-format prior to sending a code review. There is currently no Eclipse formatter, but the tool can be run from the command line:
java -jar /path/to/google-java-format-1.0-all-deps.jar -i path/to/java/File.java
CSS in Gitiles follows the SUIT CSS naming conventions.
Gitiles uses Gerrit for code review: https://gerrit-review.googlesource.com/
Gitiles uses the “git push” workflow with server https://gerrit.googlesource.com/gitiles. You will need a generated cookie.
Gerrit depends on “Change-Id” annotations in your commit message. If you try to push a commit without one, it will explain how to install the proper git-hook:
curl -Lo `git rev-parse --git-dir`/hooks/commit-msg \
https://gerrit-review.googlesource.com/tools/hooks/commit-msg
chmod +x `git rev-parse --git-dir`/hooks/commit-msg
Before you create your local commit (which you'll push to Gerrit) you will need to set your email to match your Gerrit account:
git config --local --add user.email foo@bar.com
Normally you will create code reviews by pushing for master:
git push origin HEAD:refs/for/master