BlockStorage/repertory
1
0
Fork 0
Code Issues 7 Pull Requests Releases 6 Wiki Activity

Update Providers

Scott E. Graves 2025-02-23 19:23:48 -06:00
parent 72299b0b9a
commit 02e8de6e75
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Providers.md

@ -2,7 +2,7 @@
`repertory` currently supports 3 different back-end providers: `S3`, `Sia` and `Encryption`. `repertory` currently supports 3 different back-end providers: `S3`, `Sia` and `Encryption`.
### S3 ### S3 Provider
* The S3 provider utilizes the de facto standard AWS S3 HTTP REST API via `libcurl`. * The S3 provider utilizes the de facto standard AWS S3 HTTP REST API via `libcurl`.
* An access key and secret key are required for operation, configured via `S3Config.AccessKey` and `S3Config.SecretKey` in `config.json` * An access key and secret key are required for operation, configured via `S3Config.AccessKey` and `S3Config.SecretKey` in `config.json`
@ -12,11 +12,11 @@
* Locally, files remain unencrypted. The encryption/decryption process takes place while transferring to/from the S3 provider. * Locally, files remain unencrypted. The encryption/decryption process takes place while transferring to/from the S3 provider.
* This is enabled by specifying a secure password via the `S3Config.EncryptionToken` setting in `config.json`. * This is enabled by specifying a secure password via the `S3Config.EncryptionToken` setting in `config.json`.
### Sia ### Sia Provider
* The Sia provider utilizes the `renterd` native HTTP REST API via `libcurl` * The Sia provider utilizes the `renterd` native HTTP REST API via `libcurl`
### Encryption ### Encryption Provider
#### [WIP-Use with caution] #### [WIP-Use with caution]