3
This is a TurboGears (http://www.turbogears.org) project. It can be
4
started by running the start-loggerhead.py script.
b'\\ No newline at end of file'
4
Loggerhead is a web viewer for bazaar branches. It can be used to navigate
5
a branch history, annotate files, perform searches... all the usual things.
7
This is a TurboGears (http://www.turbogears.org) project. It can be
8
started by running the 'start-loggerhead.py' script.
10
If you're not familiar with turbogears, the easiest way to get this script
11
started is to run it via::
13
$ nohup ./start-loggerhead.py &
15
and add the following lines to your apache configuration::
17
<Location "/branches/">
18
ProxyPass http://127.0.0.1:8080/
19
ProxyPassReverse http://127.0.0.1:8080/
22
The port configuration is in "dev.cfg".
24
The config file is "loggerhead.conf". In there, you can configure projects,
25
and branches per project. The idea is that you could be publishing several
26
(possibly unrelated) projects through the same loggerhead instance, and
27
several branches for the same project.
33
To speed up most operations, loggerhead will start creating two caches per
34
branch when it first launches:
36
- a revision data cache
37
- a text searching cache
39
You can put the cache folder anywhere, but I find that a folder under
40
the branch's .bzr/ folder is the simplest place.
42
The caches for a branch with 10,000 revisions take about 15 minutes each
43
on my machine, but YMMV. Once they are built, they update every six hours
44
or so but usually finish quickly (or instantly) after the initial creation.
45
Until the revision cache is built, all operations will be slow.
47
You may update the bazaar branch at any time (for example, from a cron).
48
Loggerhead will notice and refresh, and bazaar uses its own branch locking
49
to prevent corruption.
55
This is loosely based on bazaar-webserve, which was loosely based on hgweb.
56
Discussion should take place on the bazaar-dev mailing list.
added
removed
README.txt
