9
9
You may decide to make the top level directory of your branch
10
10
a network share, an approach familiar to Windows users.
11
11
Unix users might prefer access to be
12
via SFTP, a secure protocol built-in to most SSH servers.
12
via SSH, a secure protocol built-in to most SSH servers.
13
13
Bazaar is *very* flexible in this regard with support for
14
14
lots of protocols some of which are given below.
16
16
=========== ======================================================
18
18
=========== ======================================================
19
\file:// Access using the standard filesystem (default)
19
\file:// Access using the standard filesystem (default).
20
\bzr+ssh:/ Access over SSH (best remote option).
20
21
\sftp:// Access using SFTP (most SSH servers provide SFTP).
21
22
\bzr:// Fast access using the Bazaar smart server.
22
23
\ftp:// Access using passive FTP.
23
\http:// Read-only access to branches exported by a web server.
24
\http:// Access to branches exported by a web server.
25
\https:// Encrypted access to branches exported by a web server.
24
26
=========== ======================================================
26
28
As indicated above, branches are identified using URLs with the
27
29
prefix indicating the transfer technology. If no prefix is given,
28
30
normal filenames are assumed. For a complete list of supported
29
31
protocols, see the ``urlspec`` online help topic or the
30
`URL Identifiers <../user-reference/bzr_man.html#url-identifiers>`_
32
`URL Identifiers <../user-reference/index.html#url-identifiers>`_
31
33
section of the Bazaar User Reference.
33
35
URLs are normally resolved relative to the root directory of the server,
40
42
To address a path relative to your home directory on the server, use a
41
tilde like so: ``sftp://example.com/~/public_html`` should map to
43
tilde like so: ``bzr+ssh://example.com/~/public_html`` should map to
42
44
``public_html`` within your home directory.
46
.. note:: Access over HTTP or HTTPS is read-only by default.
47
See `Pushing over the HTTP smart server
48
<http_smart_server.html#pushing-over-the-http-smart-server>`_ for
49
details on configuring read-write access.
44
51
A reminder about shared repositories
45
52
------------------------------------