4
[ Version 1.6 for Bazaar 1.6 ]
4
[ version 1.2 for bazaar 1.2 ]
6
Loggerhead is a web viewer for Bazaar branches. It can be used to
6
Loggerhead is a web viewer for bazaar branches. It can be used to
7
7
navigate a branch history, annotate files, perform searches... all the
14
Loggerhead depends on SimpleTAL for templating and Paste for the
15
server. So you need these installed -- on Ubuntu you want the
16
'python-simpletal' and 'python-paste' packages installed. You need
17
version 1.2 or newer of Paste.
19
Then simply run the 'serve-branches.py' with the branch you want to
20
serve on the command line:
22
./serve-branches.py ~/path/to/branch
24
The script listens on port 8080 so head to http://localhost:8080/ in
25
your browser to see the branch. You can also pass a directory that
26
contains branches to the script, and it will serve a very simple
27
directory listing at other pages.
29
You may update the Bazaar branches being viewed at any time.
30
Loggerhead will notice and refresh, and Bazaar uses its own branch
31
locking to prevent corruption.
37
Previous versions of Loggerhead read their configuration from a config
38
file. This mode of operation is still supported by the
39
'start-loggerhead.py' script. A 'loggerhead.conf.example' file is
40
included in the source which has comments explaining the various
43
Loggerhead can then be started by running::
10
This is a TurboGears (http://www.turbogears.org) project. It can be
45
13
$ ./start-loggerhead.py
47
This will run loggerhead in the background, listening on port 8080 by
50
To stop Loggerhead, run::
15
This will run loggerhead in the background. To stop it, run::
52
17
$ ./stop-loggerhead.py
54
In the configuration file you can configure projects, and branches per
55
project. The idea is that you could be publishing several (possibly
56
unrelated) projects through the same loggerhead instance, and several
57
branches for the same project. See the "loggerhead.conf.example" file
58
included with the source.
60
A debug and access log are stored in the logs/ folder, relative to
61
the location of the start-loggerhead.py script.
64
SERVING LOGGERHEAD FROM BEHIND APACHE
65
-------------------------------------
67
If you want to view Bazaar branches from your existing Apache
68
installation, you'll need to configure Apache to proxy certain
69
requests to Loggerhead. Adding lines like this to you Apache
70
configuration is one way to do this::
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::
72
22
<Location "/branches/">
73
23
ProxyPass http://127.0.0.1:8080/
74
24
ProxyPassReverse http://127.0.0.1:8080/
77
If Paste Deploy is installed, the 'serve-branches.py' script can be
78
run behind a proxy at the root of a site, but if you're running it at
79
some path into the site, you'll need to add a 'prefix' argument to the
80
PrefixMiddleware call in the script. More flexible configuration
81
should be added soon...
87
To speed up the display of the changelog view for large trees,
88
loggerhead can be configured to cache the files changes between
89
revisions. Set the 'cachepath' value in the config file.
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.
43
To speed up operations with large branches, loggerhead can be configured
44
to create three caches per branch when it first launches:
46
- a revision data cache
47
- a cache of files changed in a revision
48
- a text searching cache
50
You can put the cache folder anywhere, but I find that a folder under
51
the branch's .bzr/ folder is the simplest 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.
95
Loggerhead is loosely based on bazaar-webserve, which was loosely
96
based on hgweb. Discussion should take place on the bazaar-dev
97
mailing list at bazaar@lists.canonical.com. You can join the list at
98
<https://lists.ubuntu.com/mailman/listinfo/bazaar>. You don't need to
99
subscribe to post, but your first post will be held briefly for manual
102
Bugs are tracked on Launchpad; start at:
104
https://bugs.launchpad.net/loggerhead
67
This is loosely based on bazaar-webserve, which was loosely based on hgweb.
68
Discussion should take place on the bazaar-dev mailing list.
added
removed
README.txt
