4
[ Version 1.6 for Bazaar 1.6 ]
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
15
1) SimpleTAL for templating.
16
on ubuntu package `sudo apt-get install python-simpletal`
17
or download from http://www.owlfish.com/software/simpleTAL/download.html
18
2) Paste for the server. (You need version 1.2 or newer of Paste.)
19
on ubuntu package `sudo apt-get install python-paste`
20
or use `easy_install Paste`
21
3) Paste Deploy (optional, needed when proxying through Apache)
22
on ubuntu package `sudo apt-get install python-pastedeploy`
23
or use `easy_install PasteDeploy`
25
Then simply run the 'serve-branches' with the branch you want to
26
serve on the command line:
28
./serve-branches ~/path/to/branch
30
The script listens on port 8080 so head to http://localhost:8080/ in
31
your browser to see the branch. You can also pass a directory that
32
contains branches to the script, and it will serve a very simple
33
directory listing at other pages.
35
You may update the Bazaar branches being viewed at any time.
36
Loggerhead will notice and refresh, and Bazaar uses its own branch
37
locking to prevent corruption.
43
Previous versions of Loggerhead read their configuration from a config
44
file. This mode of operation is still supported by the
45
'start-loggerhead' script. A 'loggerhead.conf.example' file is
46
included in the source which has comments explaining the various
49
Loggerhead can then be started by running::
53
This will run loggerhead in the background, listening on port 8080 by
56
To stop Loggerhead, run::
60
In the configuration file you can configure projects, and branches per
61
project. The idea is that you could be publishing several (possibly
62
unrelated) projects through the same loggerhead instance, and several
63
branches for the same project. See the "loggerhead.conf.example" file
64
included with the source.
66
A debug and access log are stored in the logs/ folder, relative to
67
the location of the start-loggerhead script.
70
SERVING LOGGERHEAD FROM BEHIND APACHE
71
-------------------------------------
73
If you want to view Bazaar branches from your existing Apache
74
installation, you'll need to configure Apache to proxy certain
75
requests to Loggerhead. Adding lines like this to you Apache
76
configuration is one way to do this::
4
[ version 1.0 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
10
started by running the 'start-loggerhead.py' script.
12
If you're not familiar with turbogears, the easiest way to get this script
13
started is to run it via::
15
$ nohup ./start-loggerhead.py &
17
and add the following lines to your apache configuration::
78
19
<Location "/branches/">
79
20
ProxyPass http://127.0.0.1:8080/
80
21
ProxyPassReverse http://127.0.0.1:8080/
83
If Paste Deploy is installed, the 'serve-branches' script can be
84
run behind a proxy at the root of a site, but if you're running it at
85
some path into the site, you'll need to specify is using '--prefix=/some_path'.
90
To speed up the display of the changelog view for large trees,
91
loggerhead can be configured to cache the files changes between
92
revisions. Set the 'cachepath' value in the config file.
24
The port configuration is in "dev.cfg".
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.
35
To speed up most operations, loggerhead will start creating two caches per
36
branch when it first launches:
38
- a revision data cache
39
- a text searching cache
41
You can put the cache folder anywhere, but I find that a folder under
42
the branch's .bzr/ folder is the simplest place.
44
The caches for a branch with 10,000 revisions take about 15 minutes each
45
on my machine, but YMMV. Once they are built, they update every six hours
46
or so but usually finish quickly (or instantly) after the initial creation.
47
Until the revision cache is built, all operations will be slow.
49
You may update the bazaar branch at any time (for example, from a cron).
50
Loggerhead will notice and refresh, and bazaar uses its own branch locking
51
to prevent corruption.
98
Loggerhead is loosely based on bazaar-webserve, which was loosely
99
based on hgweb. Discussion should take place on the bazaar-dev
100
mailing list at bazaar@lists.canonical.com. You can join the list at
101
<https://lists.ubuntu.com/mailman/listinfo/bazaar>. You don't need to
102
subscribe to post, but your first post will be held briefly for manual
105
Bugs are tracked on Launchpad; start at:
107
https://bugs.launchpad.net/loggerhead
57
This is loosely based on bazaar-webserve, which was loosely based on hgweb.
58
Discussion should take place on the bazaar-dev mailing list.
added
removed
README.txt
