1
=======================
2
Running a Bazaar Server
3
=======================
5
4
Bazaar does not require a specialised server because it operates over HTTP, FTP
6
5
or SFTP. There is an optional smart server that can be invoked over SSH, from
7
6
inetd, or in a dedicated mode.
12
11
We describe HTTP, FTP, SFTP and HTTP-WebDAV as "dumb" servers because they do
13
12
not offer any assistance to Bazaar. If you make a Bazaar repository available
19
18
Bazaar supports writing over FTP, SFTP and (via a plugin) over HTTP-WebDAV.
21
High-performance server
22
=======================
20
High-performance smart server
21
-----------------------------
24
The high-performance server is currently in development. It provides a dumb
25
server facility as well as additional capabilities which allow the version of
26
bzr that accompanies this documentation to perform some operations much faster
27
than via dumb servers. In future releases of bzr the range of operations that
28
are improved by using the high-performance server will increase.
23
The high-performance smart server (hpss) performs certain operations much faster
24
than dumb servers are capable of. In future releases, the range of operations
25
that are improved by using the smart server will increase as we continue to
30
28
To maintain the highest security possible, the current
31
high-performance server provides read-only access by default. To
29
smart server provides read-only access by default. To
32
30
enable read-write access, run it with ``--allow-writes``. When using
33
the SSH access method, bzr automatically runs with with the
31
the SSH access method, bzr automatically runs with the
34
32
``--allow-writes`` option.
36
The server can be configured to run in three different ways:
34
The alternative ways of configuring a smart server are explained below.
41
39
Using Bazaar over SSH requires no special configuration on the server::
61
59
Running a Bazaar server from inetd requires an inetd.conf entry::
63
4155 stream tcp nowait bzruser /usr/bin/bzr serve --inet --directory=/srv/bzr/repo
61
4155 stream tcp nowait bzruser /usr/bin/bzr /usr/bin/bzr serve --inet --directory=/srv/bzr/repo
65
63
When running client commands, the URL you supply is a `bzr://` URL relative to
66
64
the ``--directory`` option given in inetd.conf::
68
66
bzr log bzr://host/branchname
73
71
This mode has the same path and URL behaviour as the inetd mode. To
74
72
run as a specific user, you should use ``su`` or login as that user.
75
This example runs ``bzr serve`` on `localhost` port `1234`.
79
bzr serve --port=localhost:1234 --directory=/srv/bzr/repo
83
bzr log bzr://host:1234/branchname
85
74
This example runs bzr on its official port number of `4155` and listens on all
86
75
interfaces. This allows connections from anywhere in the world that can reach
87
76
your machine on port `4155`.
90
80
bzr serve --directory=/srv/bzr/repo
84
bzr log bzr://host/branchname
86
This example runs ``bzr serve`` on `localhost` port `1234`.
90
bzr serve --port=localhost:1234 --directory=/srv/bzr/repo
94
bzr log bzr://localhost:1234/branchname