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
[ version 1.1 for bazaar 0.13 ]
6
Loggerhead is a web viewer for bazaar branches. It can be used to navigate
7
a branch history, annotate files, perform searches... all the usual things.
9
This is a TurboGears (http://www.turbogears.org) project. It can be
12
$ ./start-loggerhead.py
14
This will run loggerhead in the background. To stop it, run::
16
$ ./stop-loggerhead.py
18
If you're not familiar with TurboGears, the simplest way to get running is
19
to add the following lines to your apache configuration::
21
<Location "/branches/">
22
ProxyPass http://127.0.0.1:8080/
23
ProxyPassReverse http://127.0.0.1:8080/
26
The config file is "loggerhead.conf". In there, you can configure projects,
27
and branches per project. The idea is that you could be publishing several
28
(possibly unrelated) projects through the same loggerhead instance, and
29
several branches for the same project.
31
Don't bother with "dev.cfg" or any of the other TurboGears config files.
32
Loggerhead overrides those values with its own.
34
A debug and access log are stored in the logs/ folder.
40
To speed up most operations, loggerhead will start creating two caches per
41
branch when it first launches:
43
- a revision data cache
44
- a text searching cache
46
You can put the cache folder anywhere, but I find that a folder under
47
the branch's .bzr/ folder is the simplest place.
49
The caches for a branch with 10,000 revisions take about 15 minutes each
50
on my machine, but YMMV. Once they are built, they update every six hours
51
or so but usually finish quickly (or instantly) after the initial creation.
52
Until the revision cache is built, all operations will be slow.
54
You may update the bazaar branch at any time (for example, from a cron).
55
Loggerhead will notice and refresh, and bazaar uses its own branch locking
56
to prevent corruption.
62
This is loosely based on bazaar-webserve, which was loosely based on hgweb.
63
Discussion should take place on the bazaar-dev mailing list.