octoleo/restic
2
2
Fork 0
mirror of https://github.com/octoleo/restic.git synced 2024-12-22 10:58:55 +00:00
Code Issues Releases Wiki Activity

doc: Add --cacert to REST section

Browse Source
This commit is contained in:
Alexander Neumann 2017-11-26 10:09:54 +01:00
parent 6a4a328bbc
commit abde9e2fba
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/030_preparing_a_new_repo.rst
View File

@ -135,10 +135,11 @@ are some more examples:
$ restic -r rest:https://user:pass@host:8000/ $ restic -r rest:https://user:pass@host:8000/
$ restic -r rest:https://user:pass@host:8000/my_backup_repo/ $ restic -r rest:https://user:pass@host:8000/my_backup_repo/
If you use TLS, make sure your certificates are signed, 'cause restic If you use TLS, restic will use the system's CA certificates to verify the
client will refuse to communicate otherwise. It's easy to obtain such server certificate. When the verification fails, restic refuses to proceed and
certificates today, thanks to free certificate authorities like `Let’s exits with an error. If you have your own self-signed certificate, or a custom
Encrypt <https://letsencrypt.org/>`__. CA certificate should be used for verification, you can pass restic the
certificate filename via the `--cacert` option.
REST server uses exactly the same directory structure as local backend, REST server uses exactly the same directory structure as local backend,
so you should be able to access it both locally and via HTTP, even so you should be able to access it both locally and via HTTP, even