From 6f69f38e1450c4c099798331b9b36705cc69bb31 Mon Sep 17 00:00:00 2001 From: Junxiang Huang Date: Tue, 31 Dec 2024 18:15:02 +0800 Subject: [PATCH] update 12.0 for using SeaSearch --- manual/setup/cluster_deploy_with_docker.md | 4 +-- manual/setup/setup_pro_by_docker.md | 29 ++++++++++++++-------- manual/setup_binary/cluster_deployment.md | 4 +-- 3 files changed, 22 insertions(+), 15 deletions(-) diff --git a/manual/setup/cluster_deploy_with_docker.md b/manual/setup/cluster_deploy_with_docker.md index 9b85c8f5..cd5dea93 100644 --- a/manual/setup/cluster_deploy_with_docker.md +++ b/manual/setup/cluster_deploy_with_docker.md @@ -39,9 +39,9 @@ Let's assume you have three nodes in your cluster: A, B, and C. !!! note "Prerequisites" - - We assume you have already deployed memory cache server (e.g., ***Memcached***), ***MariaDB***, ***ElasticSearch*** in separate machines and use ***S3*** like object storage. + - We assume you have already deployed memory cache server (e.g., ***Memcached***), ***MariaDB***, file indexer (e.g., ***ElasticSearch***, [*SeaSearch*](https://haiwen.github.io/seasearch-docs/)) in separate machines and use ***S3*** like object storage. - - Usually, each node of Seafile Cluster should have at least **2 cores** and **2G memory**. If the above services are deployed together with a node in the Seafile cluster, we recommend that you prepare **4 cores** and **4G memory** for the node (especially if ElasticSearch is also deployed on the node) + - Usually, each node of Seafile Cluster should have at least **2 cores** and **2G memory**. If the above services are deployed together with a node in the Seafile cluster especially ***ElasticSearch***, we recommend that you prepare **4 cores** and **4G memory** for that node Seafile Server: 2 frontend nodes, 1 backend node diff --git a/manual/setup/setup_pro_by_docker.md b/manual/setup/setup_pro_by_docker.md index 22046e19..e39f7a86 100644 --- a/manual/setup/setup_pro_by_docker.md +++ b/manual/setup/setup_pro_by_docker.md @@ -4,23 +4,30 @@ This manual explains how to deploy and run Seafile Server Professional Edition ( ## Requirements -Seafile PE requires a minimum of 2 cores and 2GB RAM. +Seafile PE docker requires a minimum of 4 cores and 4GB RAM. !!! note "Other requirements for Seafile PE" - If Elasticsearch is installed on the same server, the minimum requirements are 4 cores and 4 GB RAM, and make sure the [mmapfs counts](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-store.html#mmapfs) do not cause excptions like out of memory, which can be increased by following command (see for futher details): + - **By default**, Seafile Pro will use ***Elasticsearch*** as the files indexer - ```shell - sysctl -w vm.max_map_count=262144 #run as root - ``` + Please make sure the [mmapfs counts](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-store.html#mmapfs) do not cause excptions like out of memory, which can be increased by following command (see for futher details): - or modify **/etc/sysctl.conf** and reboot to set this value permanently: + ```shell + sysctl -w vm.max_map_count=262144 #run as root + ``` - ```shell - nano /etc/sysctl.conf + or modify **/etc/sysctl.conf** and reboot to set this value permanently: - # modify vm.max_map_count - vm.max_map_count=262144 - ``` + ```shell + nano /etc/sysctl.conf + + # modify vm.max_map_count + vm.max_map_count=262144 + ``` + - If your machine **dose not** have enough requirements, 2 Cores and 2GB RAM are minimum by chosing one of following two ways **after first-time deployment** of Seafile Pro docker: + + - Use [*SeaSearch*](https://haiwen.github.io/seasearch-docs/config/seafile.md), a lightweight search engine built on open source search engine [*ZincSearch*](https://zincsearch-docs.zinc.dev/), as the indexer + + - Deploy *Elasticsearch* in another machine, and modify `es_host` and `es_port` in [seafevents.conf](../config/seafevents-conf.md) !!! tip "About license" Seafile PE can be used without a paid license with up to three users. Licenses for more user can be purchased in the [Seafile Customer Center](https://customer.seafile.com) or contact Seafile Sales at [sales@seafile.com](mailto:sales@seafile.com). For futher details, please refer the [license page](../setup_binary/seafile_professional_sdition_software_license_agreement.md) of Seafile PE. diff --git a/manual/setup_binary/cluster_deployment.md b/manual/setup_binary/cluster_deployment.md index 4c1222f3..22f97f08 100644 --- a/manual/setup_binary/cluster_deployment.md +++ b/manual/setup_binary/cluster_deployment.md @@ -9,9 +9,9 @@ !!! note "Prerequisites" - - We assume you have already deployed memory cache server (e.g., ***Memcached***), ***MariaDB***, ***ElasticSearch*** in separate machines and use ***S3*** like object storage. + - We assume you have already deployed memory cache server (e.g., ***Memcached***), ***MariaDB***, file indexer (e.g., ***ElasticSearch***, [*SeaSearch*](https://haiwen.github.io/seasearch-docs/)) in separate machines and use ***S3*** like object storage. - - Usually, each node of Seafile Cluster should have at least **2 cores** and **2G memory**. If the above services are deployed together with a node in the Seafile cluster, we recommend that you prepare **4 cores** and **4G memory** for the node (especially if ElasticSearch is also deployed on the node) + - Usually, each node of Seafile Cluster should have at least **2 cores** and **2G memory**. If the above services are deployed together with a node in the Seafile cluster especially ***ElasticSearch***, we recommend that you prepare **4 cores** and **4G memory** for that node System: Ubuntu 24.04/22.04, Debian 12/11