7
7
Bazaar can also serve branches over protocols that know nothing about Bazaar's
8
8
specific needs. These are called "dumb servers" to distinguish them from
9
Bazaar's native protocol. Currently HTTP, FTP, SFTP and HTTP+WebDAV can be
10
used to read branches remotely. FTP, SFTP and HTTP+WebDAV can be used for
9
Bazaar's native protocol. Currently HTTP, HTTPS, FTP, SFTP and HTTP+WebDAV can
10
be used to read branches remotely. FTP, SFTP and HTTP+WebDAV can be used for
11
11
writing as well. To use any of these protocols, it is just necessary to
12
12
provide access to the server's filesystem under ``/srv/bzr``.
33
33
Smart server over HTTP(S)
34
34
-------------------------
36
Bazaar can use its native protocol with HTTP requests. Since HTTP is a network
37
protocol that is available on many networks, this can be a good option where
38
SSH access is not possible. Another benefit of this setup is that all of the
39
authentication and access control methods available to the HTTP server (basic,
40
LDAP, ActiveDirectory, etc.) are then available to control access to Bazaar
41
branches. More information about setting up this type of access using Apache
42
and FastCGI or mod_python or WSGI is in the `smart server section of the User's
43
Guide <../user-guide/http_smart_server.html>`_.
36
Bazaar can use its native protocol with HTTP or HTTPS requests. Since HTTP is
37
a network protocol that is available on many networks, this can be a good
38
option where SSH access is not possible. Another benefit of this setup is that
39
all of the authentication and access control methods available to the HTTP
40
server (basic, LDAP, ActiveDirectory, etc.) are then available to control
41
access to Bazaar branches. More information about setting up this type of
42
access using Apache and FastCGI or mod_python or WSGI is in the `smart server
43
section of the User's Guide <../user-guide/http_smart_server.html>`_.
45
45
Direct Smart Server Access
46
46
--------------------------
added
removed
doc/en/admin-guide/other-setups.txt
