mirror of
https://github.com/borgbackup/borg.git
synced 2024-12-23 08:16:54 +00:00
docs: Updated examples in deployment.rst, fixes #644
This commit is contained in:
parent
648aac5b20
commit
aeec29545e
1 changed files with 2 additions and 2 deletions
|
@ -51,7 +51,7 @@ Restrictions
|
||||||
------------
|
------------
|
||||||
|
|
||||||
Borg is instructed to restrict clients into their own paths:
|
Borg is instructed to restrict clients into their own paths:
|
||||||
``borg serve --restrict-path /home/backup/repos/<client fqdn>``
|
``borg serve --restrict-to-path /home/backup/repos/<client fqdn>``
|
||||||
|
|
||||||
There is only one ssh key per client allowed. Keys are added for ``johndoe.clnt.local``, ``web01.srv.local`` and
|
There is only one ssh key per client allowed. Keys are added for ``johndoe.clnt.local``, ``web01.srv.local`` and
|
||||||
``app01.srv.local``. But they will access the backup under only one UNIX user account as:
|
``app01.srv.local``. But they will access the backup under only one UNIX user account as:
|
||||||
|
@ -61,7 +61,7 @@ forced command and restrictions applied as shown below:
|
||||||
::
|
::
|
||||||
|
|
||||||
command="cd /home/backup/repos/<client fqdn>;
|
command="cd /home/backup/repos/<client fqdn>;
|
||||||
borg serve --restrict-path /home/backup/repos/<client fqdn>",
|
borg serve --restrict-to-path /home/backup/repos/<client fqdn>",
|
||||||
no-port-forwarding,no-X11-forwarding,no-pty,
|
no-port-forwarding,no-X11-forwarding,no-pty,
|
||||||
no-agent-forwarding,no-user-rc <keytype> <key> <host>
|
no-agent-forwarding,no-user-rc <keytype> <key> <host>
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue