Fix dev server configuration

The config option gitiles.basePath was overloaded in [1]
which broke the default behavior of gitiles in dev mode. It used to scan
the path configured via gitiles.basePath to find git repositories.

With [1] it now sets the servlet context path for gitiles to the value
of the same option which doesn't work since the dev mode by default sets
gitiles.basePath to the current working directory which doesn't work
as a servlet context path which results in gitiles returning
"404 Not Found" instead of showing the list of repositories found under
basePath.

Fix this by renaming the option introduced in [1] to
gitiles.contextPath and adapt the documentation accordingly.

[1] I1da95745d1bc8eaa7d5b204a942bcee0b6a027a8

Change-Id: I0f844eaaaadbfd21161e04b915b541a534bbb4a6
2 files changed
tree: 5530e2be9bee831ddc4f6d288c9fbe6e0188e4ac
  1. .settings/
  2. Documentation/
  3. java/
  4. javatests/
  5. lib/
  6. modules/
  7. resources/
  8. tools/
  9. .bazelrc
  10. .bazelversion
  11. .gitignore
  12. .gitmodules
  13. .mailmap
  14. .zuul.yaml
  15. BUILD
  16. COPYING
  17. fake_pom_deploy.xml
  18. navbar.md
  19. README.md
  20. version.bzl
  21. WORKSPACE
README.md

Gitiles - A simple JGit repository browser

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 automatically renders *.md Markdown files into HTML for simplified documentation. Refer to the Markdown documentation for details.

Configuration

Gitiles is configurable in a git-style configuration file named gitiles.config. Refer to the configuration documentation for details.

Bugs

Use gerrit's issue tracker to file bugs.

Contributing to Gitiles

Please refer to the Developer Guide.