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

update upgrade docker

This commit is contained in:
Junxiang Huang 2025-07-01 17:55:42 +08:00
parent 08a1d6eae6
commit 1fc7f45414
1 changed files with 13 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
manual/upgrade/upgrade_docker.md
View File

@ -126,7 +126,7 @@ If you are using notification server in Seafile 12, please specify the notificat
NOTIFICATION_SERVER_URL=http://<your notification server host>:8083
```
#### Step 3.4) Add configurations for storage backend (Optional)
#### Step 3.4) Add configurations for storage backend (Pro)
Seafile 13.0 add a new environment `SEAF_SERVER_STORAGE_TYPE` to determine the storage backend of seaf-server component. You can delete the variable or set it to empty (`SEAF_SERVER_STORAGE_TYPE=`) to use the old way, i.e., determining the storage backend from seafile.conf.
@ -138,14 +138,6 @@ Seafile 13.0 add a new environment `SEAF_SERVER_STORAGE_TYPE` to determine the s
SEAF_SERVER_STORAGE_TYPE=disk
```
=== "Use the configuration in `seafile.conf`"
If you would like to use the storage configuration in `seafile.conf`, please remove default value of `SEAF_SERVER_STORAGE_TYPE` in `.env`:
```sh
SEAF_SERVER_STORAGE_TYPE=
```
=== "S3 backend"
Set `SEAF_SERVER_STORAGE_TYPE` to `s3`, and add your s3 configurations:
@ -176,13 +168,23 @@ Seafile 13.0 add a new environment `SEAF_SERVER_STORAGE_TYPE` to determine the s
SEAF_SERVER_STORAGE_TYPE=multiple
```
=== "Use the configuration in `seafile.conf`"
If you would like to use the storage configuration in `seafile.conf`, please remove default value of `SEAF_SERVER_STORAGE_TYPE` in `.env`:
```sh
SEAF_SERVER_STORAGE_TYPE=
```
### Step 4) Remove obsolote configurations
Although the configurations in environment (i.e., `.env`) have higher priority than the configurations in config files, we recommend that you remove or modify the cache configuration in the following files to avoid ambiguity:：
- `seafile.conf`: remove the `[memcached]` section. If you are using single S3 backend and have specified `SEAF_SERVER_STORAGE_TYPE=s3` in `.env`, the `[commit_object_backend]`, `[fs_object_backend]` and `[block_backend]` also can be removed.
- `seahub_settings.py`: remove the key `default` in variable `CACHES`
- Open `/opt/seafile-data/seafile/conf/seafile.conf` and remove the entire `[memcached]`, `[commit_object_backend]`, `[fs_object_backend]` and `[block_backend]` if above sections have correctly specified in `.env`.
- Open `/opt/seafile-data/seafile/conf/seahub_settings.py` and remove the entire blocks for `DATABASES = {...}` and `CAHCES = {...}`
In the most cases, the `seafile.conf` only include the listen port `8082` of Seafile file server.
### Step 5) Start Seafile