24
by Robey Pointer
figured out how to make my own separate config file like BzrInspect, and |
1 |
# use this to change the server's port |
89
by Robey Pointer
fix up dev.cfg so that nobody will ever have to edit it, by letting the |
2 |
#server.socket_port = 8080
|
3 |
||
4 |
# use this if you're mapping loggerhead within apache via proxy |
|
5 |
#server.webpath = 'http://example.com/branches' |
|
6 |
||
7 |
# where's bzrlib? |
|
24
by Robey Pointer
figured out how to make my own separate config file like BzrInspect, and |
8 |
# (you only need this if you don't install bzr.) |
46
by Robey Pointer
add footer banners for bazaar and loggerhead, and slightly improve the config |
9 |
#bzrpath = '/Users/robey/code/bzr/bzr' |
75
by Robey Pointer
flesh out examples for the auto_publish feature. |
10 |
|
24
by Robey Pointer
figured out how to make my own separate config file like BzrInspect, and |
11 |
# if you want a special title on the front page, set it here: |
49
by Robey Pointer
add top-level page listing available branches. also a patch from matty to not require external-url in atom feeds any more |
12 |
title = 'branches in loggerhead' |
75
by Robey Pointer
flesh out examples for the auto_publish feature. |
13 |
|
49
by Robey Pointer
add top-level page listing available branches. also a patch from matty to not require external-url in atom feeds any more |
14 |
# group branches by project: |
15 |
[bazaar] |
|
16 |
||
17 |
# name of this project |
|
18 |
name = 'bazaar' |
|
19 |
|
|
75
by Robey Pointer
flesh out examples for the auto_publish feature. |
20 |
# for the top browsing page, you can include a description, in raw HTML. |
21 |
#description = 'Bazaar is a <i>revision control system</i>.' |
|
22 |
||
23 |
# should we cache revisions and build a text index? (HIGHLY recommended) |
|
24 |
# this will be a folder containing a few files. if the folder doesn't |
|
25 |
# exist, it'll be created. |
|
26 |
# |
|
27 |
# all branches in this project will share the same cache, which is usually |
|
28 |
# what you want if they share a repository. if not, you can also specify |
|
29 |
# this per-branch. |
|
30 |
cachepath = '/Users/robey/code/bzr/.bzr/loggerhead-files' |
|
31 |
||
49
by Robey Pointer
add top-level page listing available branches. also a patch from matty to not require external-url in atom feeds any more |
32 |
# each branch is in a sub-folder of the website, and the config |
33 |
# key describes that folder name: |
|
34 |
[[bzr.dev]] |
|
57
by Robey Pointer
use bzr.dev as the branch name now that it's okay |
35 |
|
49
by Robey Pointer
add top-level page listing available branches. also a patch from matty to not require external-url in atom feeds any more |
36 |
# where is the bazaar branch located? |
37 |
folder = '/Users/robey/code/bzr/bzr.dev' |
|
75
by Robey Pointer
flesh out examples for the auto_publish feature. |
38 |
|
49
by Robey Pointer
add top-level page listing available branches. also a patch from matty to not require external-url in atom feeds any more |
39 |
# (optional) is there a friendier name for the branch that i should |
40 |
# use on the web pages? |
|
41 |
# you can also define this using the branch's nickname. |
|
75
by Robey Pointer
flesh out examples for the auto_publish feature. |
42 |
#branch_name = 'bazaar-dev' |
43 |
||
49
by Robey Pointer
add top-level page listing available branches. also a patch from matty to not require external-url in atom feeds any more |
44 |
# (optional) short description for the top-level page
|
45 |
# you can also define this using the "description" config key in the
|
|
75
by Robey Pointer
flesh out examples for the auto_publish feature. |
46 |
# branch's 'branch.conf'. |
47 |
description = "bazaar vcs development branch" |
|
48 |
||
49
by Robey Pointer
add top-level page listing available branches. also a patch from matty to not require external-url in atom feeds any more |
49 |
# (optional) public branch url for the top-level page |
50 |
# you can also define this using the "public_url" config key in the |
|
75
by Robey Pointer
flesh out examples for the auto_publish feature. |
51 |
# branch's 'branch.conf'. |
52 |
url = 'http://bazaar-ng.org/bzr/bzr.dev' |
|
53 |
||
54 |
||
55 |
# here's an example of an auto-published folder: |
|
56 |
[paramiko] |
|
57 |
name = 'paramiko' |
|
58 |
cachepath = '/Users/robey/code/paramiko/.bzr/loggerhead-files' |
|
59 |
|
|
60 |
# if an auto_publish_folder is given, any bazaar branches discovered in |
|
61 |
# that folder will be published. using each branch's 'branch.conf' to |
|
62 |
# provide optional descriptions and public urls is a nice way to avoid
|
|
63 |
# having to do much configuration here.
|
|
64 |
auto_publish_folder = '/Users/robey/code/paramiko' |
|
65 |
|
|
66 |
# if all of the branches under an auto_publish_folder are exported to
|
|
67 |
# the same (base) public url, you can specify that url prefix here, and
|
|
68 |
# each discovered branch's public url will be generated. |
|
69 |
url_prefix = 'http://www.example.com/code/paramiko' |
|
70 |