update 13.0 docs

manual/config/seafevents-conf.md

@@ -3,14 +3,6 @@
 In the file `seafevents.conf`:
 
 ```
-[DATABASE]
-type = mysql
-host = 192.168.0.2
-port = 3306
-username = seafile
-password = password
-name = seahub_db
-
 [STATISTICS]
 ## must be "true" to enable statistics
 enabled = false
@@ -39,14 +31,6 @@ suffix = md,txt,...
 ## When set to 0, there is no time limit, which means that each save will generate a separate historical version.
 
 ## If you need to modify the file list format, you can add 'suffix = md, txt, ...' configuration items to achieve.
-
-# From Seafile 13.0 Redis also support using in CE, and is the default cached server
-[REDIS]
-## redis use the 0 database and "repo_update" channel
-server = 192.168.1.1
-port = 6379
-password = q!1w@#123
-
 ```
 
 

manual/config/seafile-conf.md

@@ -55,35 +55,6 @@ expire_days = 60
 
 Seafile uses a system trash, where deleted libraries will be moved to. In this way, accidentally deleted libraries can be recovered by system admin.
 
-## Cache
-
-seaf-server component in Seafile Pro Edition uses memory caches in various cases to improve performance. (seaf-server component in community edition does not use cache) Some session information is also saved into memory cache to be shared among the cluster nodes. Memcached or Reids can be use for memory cache.
-
-!!! tip
-    Redis support is added in version 11.0 and is the default cache server from Seafile 13.0. Currently only single-node Redis is supported. Redis Sentinel or Cluster is not supported yet.
-
-=== "memcached"
-
-    ```
-    [memcached]
-    # Replace `localhost` with the memcached address:port if you're using remote memcached
-    # POOL-MIN and POOL-MAX is used to control connection pool size. Usually the default is good enough.
-    memcached_options = --SERVER=localhost --POOL-MIN=10 --POOL-MAX=100
-
-    ```
-
-=== "Redis"
-
-    ```
-    [redis]
-    # your redis server address
-    redis_host = 127.0.0.1
-    # your redis server port
-    redis_port = 6379
-    # size of connection pool to redis, default is 100
-    max_connections = 100
-    ```
-
 ## Seafile fileserver configuration
 
 The configuration of seafile fileserver is in the `[fileserver]` section of the file `seafile.conf`

manual/extension/metadata-server.md

@@ -5,7 +5,7 @@ Metadata server aims to provide metadata management for your libraries, so as to
 ## Deployment
 
 !!! note "Prerequisites"
-    The startup of Metadata server requires using ***Redis*** as the cache server (it should be the default cache server in Seafile 13.0). So you must deploy *Redis* for Seafile, then modify [`seafile.conf`](../config/seafile-conf.md#cache-pro-edition-only), [`seahub_settings.py`](https://docs.djangoproject.com/en/4.2/topics/cache/#redis) and [`seafevents.conf`](../config/seafevents-conf.md) to enable it before deploying metadata server.
+    The startup of Metadata server requires using ***Redis*** as the cache server (it should be the default cache server in Seafile 13.0). So you must deploy *Redis* for Seafile, then modify [`seafile.conf`](../config/env.md#cache-configurations), [`seahub_settings.py`](https://docs.djangoproject.com/en/4.2/topics/cache/#redis) and [`seafevents.conf`](../config/seafevents-conf.md) to enable it before deploying metadata server.
 
 !!! warning
     Please make sure your Seafile service has been deployed **before** deploying Metadata server. This is because Metadata server needs to read Seafile's configuration file `seafile.conf`. If you deploy Metadata server before or at the same time with Seafile, it may not be able to detect `seafile.conf` and fail to start.

manual/setup/setup_with_ceph.md

@@ -48,7 +48,7 @@ ceph_config = /etc/ceph/ceph.conf
 pool = seafile-fs
 ```
 
-!!! note "You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only)"
+!!! note "You also need to add [memory cache configurations](../config/env.md#cache-configurations)"
 
 It's required to create separate pools for commit, fs, and block objects.
 

manual/setup/setup_with_multiple_storage_backends.md

@@ -50,7 +50,7 @@ By default, Seafile dose not enable multiple storage classes. So, you have to cr
     * `storage_classes_file：Specifies` the path for the **JSON** file that contains the storage class definition.
 
     !!! tip 
-        - Make sure you have added [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only) to `seafile.conf`
+        - Make sure you have added [memory cache configurations](../config/env.md#cache-configurations) to `seafile.conf`
         - Due to the *Docker persistence strategy*, the path of `storage_classes_file` **in the *Seafile container*** is different from the host usually, so we suggest you put this file in to the Seafile's configurations directory, and use `/shared/conf` instead of `/opt/seafile-date/seafile/conf`. Otherwise you have to add another persistent volume mapping strategy in `seafile-server.yml`. If your Seafile server is not deployed with Docker, we still suggest you put this file into the Seafile configurations file directory.
 
 ## Exmaple of storage classes file

manual/setup/setup_with_s3.md

@@ -18,7 +18,7 @@ From Seafile 13, there are two ways to configure S3 storage (**single S3 storage
     
         For best performance, Seafile requires enable memory cache for objects. We recommend to **at least allocate 128MB** memory for memcached or Redis.
 
-        The configuration options differ for different S3 storage. We'll describe the configurations in separate sections. You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only)
+        The configuration options differ for different S3 storage. We'll describe the configurations in separate sections. You also need to add [memory cache configurations](../config/env.md#cache-configurations)
 
 ## Setup swith environment variables (recommend)
 

manual/setup/setup_with_swift.md

@@ -48,7 +48,7 @@ region = yourRegion
 
 ```
 
-!!! note "You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only)"
+!!! note "You also need to add [memory cache configurations](../config/env.md#cache-configurations)"
 
 The above config is just an example. You should replace the options according to your own environment.