minor doc fixes

This commit is contained in:
Nicola Murino 2021-05-20 18:34:38 +02:00
parent ecfed4dc04
commit 9fc4be6d40
No known key found for this signature in database
GPG key ID: 2F1FB59433D5A8CB
2 changed files with 15 additions and 6 deletions

View file

@ -82,8 +82,8 @@ Some Linux distro packages are available:
On Windows you can use:
- the Windows installer to install and run SFTPGo as a Windows service
- the portable package to start SFTPGo on demand
- The Windows installer to install and run SFTPGo as a Windows service.
- The portable package to start SFTPGo on demand.
You can easily test new features selecting a commit from the [Actions](https://github.com/drakkan/sftpgo/actions) page and downloading the matching build artifacts for Linux, macOS or Windows. GitHub stores artifacts for 90 days.

View file

@ -98,19 +98,28 @@ Each user can browse and download their files and change their credentials using
The procedure is similar to the one described for local users, you have only specify the Cloud Storage backend and its credentials.
The screenshot below shows an example configuration for an S3 backend.
![S3 user](./img/s3-user.png)
The screenshot below shows an example configuration for an Azure Blob Storage backend.
![Azure Blob user](./img/az-user.png)
The screenshot below shows an example configuration for a Google Cloud Storage backend.
![Google Cloud user](./img/gcs-user.png)
The screenshot below shows an example configuration for an SFTP server as storage backend.
![User using another SFTP server as storage backend](./img/sftp-user.png)
Setting a `Key Prefix` restricts the user to a specific "folder" in the bucket, so that the same bucket can be shared among different users by assigning to each user a specific portion of the bucket.
Setting a `Key Prefix` you restrict the user to a specific "folder" in the bucket, so that the same bucket can be shared among different users by assigning to each user a specific portion of the bucket.
### Creating users with a local encrypted backend (Data At Rest Encryption)
The procedure is similar to the one described for local users, you have only specify the encryption passphrase.
The screenshot below shows an example configuration.
![User with cryptfs backend](./img/local-encrypted.png)
@ -171,12 +180,12 @@ Suppose we created two folders name `localfolder` and `minio` as you can see in
![Folders](./img/folders.png)
- `localfolder` use the local filesystem as storage backend
- `minio` use MinIO (S3 compatible) as storage backend
- `localfolder` uses the local filesystem as storage backend
- `minio` uses MinIO (S3 compatible) as storage backend
Now, click `Users`, on the left menu, select a user and click the `Edit` icon, to update the user and associate the virtual folders.
Virtual folders must be referenced using their unique name and we expose them on a configurable virtual path. Take a look at the following screenshot.
Virtual folders must be referenced using their unique name and you can expose them on a configurable virtual path. Take a look at the following screenshot.
![Virtual Folders](./img/virtual-folders.png)