From 58ff499d424537b2348744b89f7407769e4eb798 Mon Sep 17 00:00:00 2001 From: Daniel Pan Date: Tue, 12 Nov 2024 15:10:27 +0800 Subject: [PATCH] Add mark for documents that need improvements --- manual/extension/distributed_indexing.md | 5 + manual/extension/fuse.md | 5 + manual/extension/virus_scan_with_kav4fs.md | 5 + manual/setup/cluster_deploy_with_k8s.md | 5 + manual/setup/migrate_backends_data.md | 5 + manual/setup/migrate_ce_to_pro_with_docker.md | 4 + manual/setup/migrate_non_docker_to_docker.md | 5 + manual/setup/setup_ce_by_docker.md | 5 + manual/setup/setup_with_amazon_s3.md | 5 + .../setup_with_multiple_storage_backends.md | 5 + manual/setup/setup_with_oss.md | 100 ------------------ mkdocs.yml | 1 - 12 files changed, 49 insertions(+), 101 deletions(-) delete mode 100644 manual/setup/setup_with_oss.md diff --git a/manual/extension/distributed_indexing.md b/manual/extension/distributed_indexing.md index 101fe78f..0c2923b3 100644 --- a/manual/extension/distributed_indexing.md +++ b/manual/extension/distributed_indexing.md @@ -1,3 +1,8 @@ +--- +status: new +--- + + # Distributed indexing If you use a cluster to deploy Seafile, you can use distributed indexing to realize real-time indexing and improve indexing efficiency. The indexing process is as follows: diff --git a/manual/extension/fuse.md b/manual/extension/fuse.md index d209800c..5f100402 100644 --- a/manual/extension/fuse.md +++ b/manual/extension/fuse.md @@ -1,3 +1,8 @@ +--- +status: new +--- + + # FUSE extension Files in the seafile system are split to blocks, which means what are stored on your seafile server are not complete files, but blocks. This design faciliates effective data deduplication. diff --git a/manual/extension/virus_scan_with_kav4fs.md b/manual/extension/virus_scan_with_kav4fs.md index 214299b9..7038cce5 100644 --- a/manual/extension/virus_scan_with_kav4fs.md +++ b/manual/extension/virus_scan_with_kav4fs.md @@ -1,3 +1,8 @@ +--- +status: new +--- + + # Virus Scan with kav4fs ## Prerequisite diff --git a/manual/setup/cluster_deploy_with_k8s.md b/manual/setup/cluster_deploy_with_k8s.md index 0b49f23d..eed6a7b5 100644 --- a/manual/setup/cluster_deploy_with_k8s.md +++ b/manual/setup/cluster_deploy_with_k8s.md @@ -1,3 +1,8 @@ +--- +status: new +--- + + # Setup with Kubernetes This manual explains how to deploy and run Seafile Server on a Linux server using Kubernetes (k8s thereafter). diff --git a/manual/setup/migrate_backends_data.md b/manual/setup/migrate_backends_data.md index fedf0eb0..fd3ef6ae 100644 --- a/manual/setup/migrate_backends_data.md +++ b/manual/setup/migrate_backends_data.md @@ -1,3 +1,8 @@ +--- +status: new +--- + + # Migrate data between different backends Seafile supports data migration between filesystem, s3, ceph, swift and Alibaba oss. diff --git a/manual/setup/migrate_ce_to_pro_with_docker.md b/manual/setup/migrate_ce_to_pro_with_docker.md index 8ca993d0..15947c3c 100644 --- a/manual/setup/migrate_ce_to_pro_with_docker.md +++ b/manual/setup/migrate_ce_to_pro_with_docker.md @@ -1,3 +1,7 @@ +--- +status: new +--- + # Migrate CE to Pro with Docker ## Preparation diff --git a/manual/setup/migrate_non_docker_to_docker.md b/manual/setup/migrate_non_docker_to_docker.md index c18c68b8..042e6c15 100644 --- a/manual/setup/migrate_non_docker_to_docker.md +++ b/manual/setup/migrate_non_docker_to_docker.md @@ -1,3 +1,8 @@ +--- +status: new +--- + + # Migrate from non-docker Seafile deployment to docker The recommended steps to migrate from non-docker deployment to docker deployment are: diff --git a/manual/setup/setup_ce_by_docker.md b/manual/setup/setup_ce_by_docker.md index 770f6d58..d7c7f2c3 100644 --- a/manual/setup/setup_ce_by_docker.md +++ b/manual/setup/setup_ce_by_docker.md @@ -1,3 +1,8 @@ +--- +status: new +--- + + # Installation of Seafile Server Community Edition with Docker ## Requirements diff --git a/manual/setup/setup_with_amazon_s3.md b/manual/setup/setup_with_amazon_s3.md index b6ecc5f5..0f3b80f3 100644 --- a/manual/setup/setup_with_amazon_s3.md +++ b/manual/setup/setup_with_amazon_s3.md @@ -1,3 +1,8 @@ +--- +status: new +--- + + # Setup With S3 Storage !!! tip "New feature from 12.0 pro edition" diff --git a/manual/setup/setup_with_multiple_storage_backends.md b/manual/setup/setup_with_multiple_storage_backends.md index f7de5a93..d652f3bd 100644 --- a/manual/setup/setup_with_multiple_storage_backends.md +++ b/manual/setup/setup_with_multiple_storage_backends.md @@ -1,3 +1,8 @@ +--- +status: new +--- + + # Multiple Storage Backend There are some use cases that supporting multiple storage backends in Seafile server is needed. Such as: diff --git a/manual/setup/setup_with_oss.md b/manual/setup/setup_with_oss.md deleted file mode 100644 index 5a126c90..00000000 --- a/manual/setup/setup_with_oss.md +++ /dev/null @@ -1,100 +0,0 @@ -# Setup With Alibaba OSS - -## Prepare - -To setup Seafile Professional Server with Alibaba OSS: - -* Setup the basic Seafile Professional Server following the guide on [Download and setup Seafile Professional Server](../setup_binary/installation_pro.md) -* Install the python `oss2` library: `sudo pip install oss2==2.3.0`.For more installation help, please refer to [this document](https://www.alibabacloud.com/help/en/object-storage-service/latest/python-preface). -* Install and configure memcached or Redis. For best performance, Seafile requires enable memory cache for objects. We recommend to allocate at least 128MB memory for Memcached or Redis. - -## Modify Seafile.conf - -Edit `seafile.conf`, add the following lines: -``` -[commit_object_backend] -name = oss -bucket = -key_id = -key = -region = beijing - -[fs_object_backend] -name = oss -bucket = -key_id = -key = -region = beijing - -[block_backend] -name = oss -bucket = -key_id = -key = -region = beijing -``` - -!!! note "You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only)" - -It's required to create separate buckets for commit, fs, and block objects. For performance and to save network traffic costs, you should create buckets within the region where the seafile server is running. - -The key_id and key are required to authenticate you to OSS. You can find the key_id and key in the "security credentials" section on your OSS management page. - -The region is the region where the bucket you created is located, such as beijing, hangzhou, shenzhen, etc. - -### Use OSS in VPC - -Before version 6.0.9, Seafile only supports using OSS services in the classic network environment. The OSS service address in the VPC (Virtual Private Network) environment is different from the classic network, so you need to specify the OSS access address in the configuration environment. After version 6.0.9, it supports the configuration of OSS access addresses, thus adding the support for VPC OSS services. - -Use the following configuration: - -``` -[commit_object_backend] -name = oss -bucket = -key_id = -key = -endpoint = vpc100-oss-cn-beijing.aliyuncs.com - -[fs_object_backend] -name = oss -bucket = -key_id = -key = -endpoint = vpc100-oss-cn-beijing.aliyuncs.com - -[block_backend] -name = oss -bucket = -key_id = -key = -endpoint = vpc100-oss-cn-beijing.aliyuncs.com - -``` - -Compared with the configuration under the classic network, the above configuration uses the `endpoint` option to replace the `region` option. The corresponding `endpoint` address can be found at . - -`endpoint` is a general option, you can also set it to the OSS access address under the classic network, and it will work as well. - -!!! note "You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only)" - -### Use HTTPS connections to OSS - -To use HTTPS connections to OSS, add the following options to seafile.conf: - -``` -[commit_object_backend] -name = oss -...... -use_https = true - -[fs_object_backend] -name = oss -...... -use_https = true - -[block_backend] -name = oss -...... -use_https = true -``` diff --git a/mkdocs.yml b/mkdocs.yml index d29f6658..dd3cc298 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -92,7 +92,6 @@ nav: - S3 Backend: setup/setup_with_amazon_s3.md - Ceph Backend: setup/setup_with_ceph.md - OpenStack Swift Backend: setup/setup_with_swift.md - - Alibaba OSS: setup/setup_with_oss.md - Multiple Storage Backends: setup/setup_with_multiple_storage_backends.md - Data migration: setup/migrate_backends_data.md - Seafile Docker autostart: setup/seafile_docker_autostart.md