Skip to content

Commit fd6e4f0

Browse files
authored
fix wrong [storage backend] in s3 configuration (#161)
1 parent 32858b7 commit fd6e4f0

File tree

1 file changed

+3
-3
lines changed
  • docs/config/enterprise

1 file changed

+3
-3
lines changed

docs/config/enterprise/S3.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ SeaTable allows the use of S3 from AWS or any other S3 compatible object storage
3030

3131
## Use S3 for base snapshots
3232

33-
The storage of base snapshots are configured in `dtable-storage-server.conf`. By default the section `[storage_backend]` contains `type = local`. With this setting, all base snapshots are stored in the folder `/opt/seatable/seatable-data/seatable/storage-data`.
33+
The storage of base snapshots are configured in `dtable-storage-server.conf`. By default the section `[storage backend]` contains `type = local`. With this setting, all base snapshots are stored in the folder `/opt/seatable/seatable-data/seatable/storage-data`.
3434

3535
Switch the type to `type = s3` to use S3 Object storage. Depending on whether you are using AWS or an S3 compatible service, different configuration options must be used.
3636

@@ -39,7 +39,7 @@ Switch the type to `type = s3` to use S3 Object storage. Depending on whether yo
3939
AWS requires only a few settings. `key_id` and `key` are used to provide S3 authentication. You can find the `key_id` and `key` in the *Security Credentials* section of your AWS account page.
4040

4141
```
42-
[storage_backend]
42+
[storage backend]
4343
type = s3
4444
bucket = ...
4545
key_id =
@@ -67,7 +67,7 @@ Switch the type to `type = s3` to use S3 Object storage. Depending on whether yo
6767
Use the following settings to connect to your S3 compatible storage.
6868

6969
```
70-
[storage_backend]
70+
[storage backend]
7171
type = s3
7272
bucket = ...
7373
host = ...

0 commit comments

Comments
 (0)