From 4365c790a21ca6b75e1918ea33f2f56cd023d69a Mon Sep 17 00:00:00 2001 From: Junxiang Huang Date: Mon, 14 Jul 2025 11:30:49 +0800 Subject: [PATCH] update descriptions --- manual/setup/helm_chart_single_node.md | 6 ++---- manual/setup/k8s_single_node.md | 7 +++---- 2 files changed, 5 insertions(+), 8 deletions(-) diff --git a/manual/setup/helm_chart_single_node.md b/manual/setup/helm_chart_single_node.md index 3c210449..ed8f7ce8 100644 --- a/manual/setup/helm_chart_single_node.md +++ b/manual/setup/helm_chart_single_node.md @@ -111,9 +111,7 @@ After installing the chart, the Seafile pod should startup automaticlly. The default service type of Seafile is ***LoadBalancer***. You should specify K8S load balancer for Seafile or specify at least one external ip, that can be accessed from external networks. !!! warning "Important for deployment" - By default, Seafile will access the ***Redis*** (the default cache from Seafile 13) and ***Elasticsearch*** (Pro only) with the specific service name: - - - ***Redis***: `redis` with port 6379 + By default, Seafile will access the ***Elasticsearch*** (Pro only) with the specific service name: - ***Elasticsearch***: `elasticsearch` with port 9200 If the above services are: @@ -122,7 +120,7 @@ After installing the chart, the Seafile pod should startup automaticlly. - With different service name - With different server port - Please modfiy the files in `/opt/seafile-data/seafile/conf` (especially the `seafevents.conf`, `seafile.conf` and `seahub_settings.py`) to make correct the configurations for above services, otherwise the Seafile server cannot start normally. Then restart Seafile server: + Please modfiy the files in `/opt/seafile-data/seafile/conf` to make correct the configurations for above services, otherwise the Seafile server cannot start normally. Then restart Seafile server: ```sh kubectl delete pods -n seafile $(kubectl get pods -n seafile -o jsonpath='{.items[*].metadata.name}' | grep seafile) diff --git a/manual/setup/k8s_single_node.md b/manual/setup/k8s_single_node.md index 3546ee5c..4385ed4e 100644 --- a/manual/setup/k8s_single_node.md +++ b/manual/setup/k8s_single_node.md @@ -12,7 +12,7 @@ Please refer [here](./system_requirements.md) for the details of system requirem For persisting data using in the docker-base deployment, `/opt/seafile-data`, is still adopted in this manual. What's more, all K8S YAML files will be placed in `/opt/seafile-k8s-yaml` (replace it when following these instructions if you would like to use another path). -By the way, we don't provide the deployment methods of basic services (e.g., **Memcached**, **MySQL** and **Elasticsearch**) and seafile-compatibility components (e.g., **SeaDoc**) for K8S in our document. If you need to install these services in K8S format, ***you can refer to the rewrite method of this document.*** +By the way, we don't provide the deployment methods of basic services (e.g., **Redis**, **MySQL** and **Elasticsearch**) and seafile-compatibility components (e.g., **SeaDoc**) for K8S in our document. If you need to install these services in K8S format, ***you can refer to the rewrite method of this document.*** ## Down load the YAML files for Seafile Server @@ -84,9 +84,8 @@ kubectl apply -f /opt/seafile-k8s-yaml/ -n seafile ``` !!! warning "Important for Pro edition" - By default, Seafile (***Pro***) will access the ***Memcached*** and ***Elasticsearch*** with the specific service name: + By default, Seafile (***Pro***) will access the ***Elasticsearch*** with the specific service name: - - ***Memcached***: `memcached` with port 11211 - ***Elasticsearch***: `elasticsearch` with port 9200 If the above services are: @@ -95,7 +94,7 @@ kubectl apply -f /opt/seafile-k8s-yaml/ -n seafile - With different service name - With different server port - Please modfiy the files in `/opt/seafile-data/seafile/conf` (especially the `seafevents.conf`, `seafile.conf` and `seahub_settings.py`) to make correct the configurations for above services, otherwise the Seafile server cannot start normally. Then restart Seafile server: + Please modfiy the files in `/opt/seafile-data/seafile/conf/seafevents.conf` to make correct the configurations for above services, otherwise the Seafile server cannot start normally. Then restart Seafile server: ```sh kubectl delete pods -n seafile $(kubectl get pods -n seafile -o jsonpath='{.items[*].metadata.name}' | grep seafile)