15308555518/ seafile-admin-docs
1
0
Fork 0
mirror of https://github.com/haiwen/seafile-admin-docs.git synced 2025-12-26 02:32:50 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

perf: Priority issues for S3_HOST and S3_AWS_REGION in 12.0

This commit is contained in:
Junxiang Huang 2025-04-24 12:05:23 +08:00
parent fdc855e1c5
commit e11ea0225b
11 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
manual/config/env.md
View File

@ -126,7 +126,7 @@ NOTIFICATION_SERVER_VOLUME=/opt/notification-data
- `INIT_S3_SECRET_KEY`: S3 storage backend secret key
- `INIT_S3_USE_V4_SIGNATURE`: Use the v4 protocol of S3 if enabled, default is `true`
- `INIT_S3_AWS_REGION`: Region of your buckets (AWS only), default is `us-east-1`. (Only valid when `INIT_S3_USE_V4_SIGNATURE` sets to `true`)
- `INIT_S3_HOST`: Host of your buckets, default is `s3.us-east-1.amazonaws.com`. (Only valid when `INIT_S3_USE_V4_SIGNATURE` sets to `true`)
- `INIT_S3_HOST`: Host of your buckets (Only required when not use AWS).
- `INIT_S3_USE_HTTPS`: Use HTTPS connections to S3 if enabled, default is `true`
## SeaSearch

2
manual/repo/docker/cluster/env
View File

@ -35,7 +35,7 @@ INIT_S3_KEY_ID=<your-key-id>
INIT_S3_SECRET_KEY=<your-secret-key>
INIT_S3_USE_V4_SIGNATURE=true
INIT_S3_AWS_REGION=us-east-1
INIT_S3_HOST=s3.us-east-1.amazonaws.com
INIT_S3_HOST=
INIT_S3_USE_HTTPS=true
JWT_PRIVATE_KEY=<your jwt private key>

2
manual/repo/docker/cluster/seafile-server.yml
View File

@ -34,7 +34,7 @@ services:
- INIT_S3_SECRET_KEY=${INIT_S3_SECRET_KEY:-}
- INIT_S3_USE_V4_SIGNATURE=${INIT_S3_USE_V4_SIGNATURE:-true}
- INIT_S3_AWS_REGION=${INIT_S3_AWS_REGION:-us-east-1}
- INIT_S3_HOST=${INIT_S3_HOST:-s3.us-east-1.amazonaws.com}
- INIT_S3_HOST=${INIT_S3_HOST:-}
- INIT_S3_USE_HTTPS=${INIT_S3_USE_HTTPS:-true}
- JWT_PRIVATE_KEY=${JWT_PRIVATE_KEY:?Variable is not set or empty}
- SEAFILE_LOG_TO_STDOUT=${SEAFILE_LOG_TO_STDOUT:-false}

4
manual/repo/docker/pro/env
View File

@ -47,7 +47,7 @@ INIT_S3_KEY_ID=<your-key-id>
INIT_S3_SECRET_KEY=<your-secret-key>
INIT_S3_USE_V4_SIGNATURE=true
INIT_S3_AWS_REGION=us-east-1
INIT_S3_HOST=s3.us-east-1.amazonaws.com
INIT_S3_HOST=
INIT_S3_USE_HTTPS=true
# SeaDoc service
@ -76,7 +76,7 @@ SS_MAX_OBJ_CACHE_SIZE=10GB
SS_S3_USE_V4_SIGNATURE=false
SS_S3_ACCESS_ID=<your access id>
SS_S3_ACCESS_SECRET=<your access secret>
SS_S3_ENDPOINT=s3.us-east-1.amazonaws.com
SS_S3_ENDPOINT=
SS_S3_BUCKET=<your bucket name>
SS_S3_USE_HTTPS=true
SS_S3_PATH_STYLE_REQUEST=true

2
manual/repo/docker/pro/seafile-server.yml
View File

@ -84,7 +84,7 @@ services:
- INIT_S3_SECRET_KEY=${INIT_S3_SECRET_KEY:-}
- INIT_S3_USE_V4_SIGNATURE=${INIT_S3_USE_V4_SIGNATURE:-true}
- INIT_S3_AWS_REGION=${INIT_S3_AWS_REGION:-us-east-1}
- INIT_S3_HOST=${INIT_S3_HOST:-us-east-1}
- INIT_S3_HOST=${INIT_S3_HOST:-}
- INIT_S3_USE_HTTPS=${INIT_S3_USE_HTTPS:-true}
labels:
caddy: ${SEAFILE_SERVER_PROTOCOL:-http}://${SEAFILE_SERVER_HOSTNAME:?Variable is not set or empty}

2
manual/repo/docker/pro/seasearch.yml
View File

@ -12,7 +12,7 @@ services:
- SS_S3_ACCESS_ID=${SS_S3_ACCESS_ID:-}
- SS_S3_USE_V4_SIGNATURE=${SS_S3_USE_V4_SIGNATURE:-false}
- SS_S3_ACCESS_SECRET=${SS_S3_ACCESS_SECRET:-}
- SS_S3_ENDPOINT=${SS_S3_ENDPOINT:-s3.us-east-1.amazonaws.com`}
- SS_S3_ENDPOINT=${SS_S3_ENDPOINT:-}
- SS_S3_BUCKET=${SS_S3_BUCKET:-}
- SS_S3_USE_HTTPS=${SS_S3_USE_HTTPS:-true}
- SS_S3_PATH_STYLE_REQUEST=${SS_S3_PATH_STYLE_REQUEST:-true}

2
manual/repo/k8s/cluster/seafile-env.yaml
View File

@ -39,5 +39,5 @@ data:
INIT_S3_KEY_ID: ""
INIT_S3_USE_V4_SIGNATURE: "true"
INIT_S3_AWS_REGION: "us-east-1"
INIT_S3_HOST: "s3.us-east-1.amazonaws.com"
INIT_S3_HOST: ""
INIT_S3_USE_HTTPS: "true"

2
manual/repo/k8s/pro/seafile-env.yaml
View File

@ -33,5 +33,5 @@ data:
INIT_S3_KEY_ID: ""
INIT_S3_USE_V4_SIGNATURE: "true"
INIT_S3_AWS_REGION: "us-east-1"
INIT_S3_HOST: "s3.us-east-1.amazonaws.com"
INIT_S3_HOST: ""
INIT_S3_USE_HTTPS: "true"

2
manual/setup/setup_pro_by_docker.md
View File

@ -75,7 +75,7 @@ The following fields merit particular attention:
| `INIT_S3_SECRET_KEY` | S3 storage backend secret key (only valid when `INIT_S3_STORAGE_BACKEND_CONFIG` sets to `true`) | (required when `INIT_S3_STORAGE_BACKEND_CONFIG` sets to `true`) |
| `INIT_S3_USE_V4_SIGNATURE` | Use the v4 protocol of S3 if enabled (only valid when `INIT_S3_STORAGE_BACKEND_CONFIG` sets to `true`) | `true` |
| `INIT_S3_AWS_REGION` | Region of your buckets (only valid when `INIT_S3_STORAGE_BACKEND_CONFIG` and `INIT_S3_USE_V4_SIGNATURE` sets to `true`) | `us-east-1` |
| `INIT_S3_HOST` | Host of your buckets (only valid when `INIT_S3_STORAGE_BACKEND_CONFIG` and `INIT_S3_USE_V4_SIGNATURE` sets to `true`) | `s3.us-east-1.amazonaws.com` |
| `INIT_S3_HOST` | Host of your buckets (only valid when `INIT_S3_STORAGE_BACKEND_CONFIG` and `INIT_S3_USE_V4_SIGNATURE` sets to `true`) | (required when not use AWS) |
| `INIT_S3_USE_HTTPS` | Use HTTPS connections to S3 if enabled (only valid when `INIT_S3_STORAGE_BACKEND_CONFIG` sets to `true`) | `true` |
To conclude, set the directory permissions of the Elasticsearch volumne:

2
manual/setup/setup_with_s3.md
View File

@ -29,7 +29,7 @@
INIT_S3_SECRET_KEY=<your-secret-key>
INIT_S3_USE_V4_SIGNATURE=true
INIT_S3_AWS_REGION=us-east-1 # your AWS Region
INIT_S3_HOST=s3.us-east-1.amazonaws.com # your S3 Host
INIT_S3_HOST= # your S3 Host
INIT_S3_USE_HTTPS=true
```

2
manual/setup/use_other_reverse_proxy.md
View File

@ -78,7 +78,7 @@ services:
- INIT_S3_SECRET_KEY=${INIT_S3_SECRET_KEY:-}
- INIT_S3_USE_V4_SIGNATURE=${INIT_S3_USE_V4_SIGNATURE:-true}
- INIT_S3_AWS_REGION=${INIT_S3_AWS_REGION:-us-east-1}
- INIT_S3_HOST=${INIT_S3_HOST:-us-east-1}
- INIT_S3_HOST=${INIT_S3_HOST:-}
- INIT_S3_USE_HTTPS=${INIT_S3_USE_HTTPS:-true}
# please remove the label section
depends_on: