4
[ Version 1.2 for Bazaar 1.2 ]
6
Loggerhead is a web viewer for Bazaar branches. It can be used to
7
navigate a branch history, annotate files, perform searches... all the
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.
10
7
This is a TurboGears (http://www.turbogears.org) project. It can be
13
$ ./start-loggerhead.py
15
This will run loggerhead in the background. To stop it, run::
17
$ ./stop-loggerhead.py
19
If you're not familiar with TurboGears, the simplest way to get running
20
is to add the lines like the following to your apache configuration::
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::
22
17
<Location "/branches/">
23
18
ProxyPass http://127.0.0.1:8080/
24
19
ProxyPassReverse http://127.0.0.1:8080/
27
The config file is "loggerhead.conf". In there, you can configure
28
projects, and branches per project. The idea is that you could be
29
publishing several (possibly unrelated) projects through the same
30
loggerhead instance, and several branches for the same project. A
31
commented example of a configuration file is loggerhead.conf.example
32
included with the source.
34
Don't bother with "dev.cfg" or any of the other TurboGears config files.
35
Loggerhead overrides those values with its own.
37
A debug and access log are stored in the logs/ folder.
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.
43
To speed up operations with large branches, loggerhead can be configured
44
to create three caches per branch when it first launches:
33
To speed up most operations, loggerhead will start creating two caches per
34
branch when it first launches:
46
36
- a revision data cache
47
- a cache of files changed in a revision
48
37
- a text searching cache
50
You can put the cache folder anywhere. A folder under the branch's
51
.bzr/ folder is a convenient place.
53
The revision data cache and text searching cache will be automatically
54
filled once loggerhead starts up. The caches for a branch with 15,000
55
revisions take about four minutes each on a fairly fast machine, but
56
mileage may vary. Once they are built, they update every six hours or
57
so but usually finish quickly (or instantly) after the initial creation.
59
You may update the Bazaar branch at any time (for example, from a cron).
60
Loggerhead will notice and refresh, and Bazaar uses its own branch
61
locking to prevent corruption.
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.
added
removed
README.txt
