mirror of
https://github.com/haiwen/seafile-admin-docs.git
synced 2025-12-26 02:32:50 +00:00
Add mark for documents that need improvements
This commit is contained in:
Daniel Pan
parent
df576ff15d
commit
58ff499d42
|
|
@ -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:
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,8 @@
|
|||
---
|
||||
status: new
|
||||
---
|
||||
|
||||
|
||||
# Virus Scan with kav4fs
|
||||
|
||||
## Prerequisite
|
||||
|
|
|
|||
|
|
@ -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).
|
||||
|
|
|
|||
|
|
@ -1,3 +1,8 @@
|
|||
---
|
||||
status: new
|
||||
---
|
||||
|
||||
|
||||
# Migrate data between different backends
|
||||
|
||||
Seafile supports data migration between filesystem, s3, ceph, swift and Alibaba oss.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
status: new
|
||||
---
|
||||
|
||||
# Migrate CE to Pro with Docker
|
||||
|
||||
## Preparation
|
||||
|
|
|
|||
|
|
@ -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:
|
||||
|
|
|
|||
|
|
@ -1,3 +1,8 @@
|
|||
---
|
||||
status: new
|
||||
---
|
||||
|
||||
|
||||
# Installation of Seafile Server Community Edition with Docker
|
||||
|
||||
## Requirements
|
||||
|
|
|
|||
|
|
@ -1,3 +1,8 @@
|
|||
---
|
||||
status: new
|
||||
---
|
||||
|
||||
|
||||
# Setup With S3 Storage
|
||||
|
||||
!!! tip "New feature from 12.0 pro edition"
|
||||
|
|
|
|||
|
|
@ -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:
|
||||
|
|
|
|||
|
|
@ -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 = <your-seafile-commits-bucket>
|
||||
key_id = <your-key-id>
|
||||
key = <your-key>
|
||||
region = beijing
|
||||
|
||||
[fs_object_backend]
|
||||
name = oss
|
||||
bucket = <your-seafile-fs-bucket>
|
||||
key_id = <your-key-id>
|
||||
key = <your-key>
|
||||
region = beijing
|
||||
|
||||
[block_backend]
|
||||
name = oss
|
||||
bucket = <your-seafile-blocks-bucket>
|
||||
key_id = <your-key-id>
|
||||
key = <your-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 = <your-seafile-commits-bucket>
|
||||
key_id = <your-key-id>
|
||||
key = <your-key>
|
||||
endpoint = vpc100-oss-cn-beijing.aliyuncs.com
|
||||
|
||||
[fs_object_backend]
|
||||
name = oss
|
||||
bucket = <your-seafile-fs-bucket>
|
||||
key_id = <your-key-id>
|
||||
key = <your-key>
|
||||
endpoint = vpc100-oss-cn-beijing.aliyuncs.com
|
||||
|
||||
[block_backend]
|
||||
name = oss
|
||||
bucket = <your-seafile-blocks-bucket>
|
||||
key_id = <your-key-id>
|
||||
key = <your-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 <https://www.alibabacloud.com/help/en/object-storage-service/latest/regions-and-endpoints>.
|
||||
|
||||
`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
|
||||
```
|
||||
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in New Issue