From 65d902077a2e5f61534e8a45cefcf92a5404bb37 Mon Sep 17 00:00:00 2001 From: Jiaqiang Xu Date: Fri, 22 Mar 2024 10:45:43 +0800 Subject: [PATCH] Fix links to cacch config file. (#264) --- manual/deploy_pro/setup_with_amazon_s3.md | 4 ++-- manual/deploy_pro/setup_with_ceph.md | 2 +- manual/deploy_pro/setup_with_oss.md | 4 ++-- manual/deploy_pro/setup_with_swift.md | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/manual/deploy_pro/setup_with_amazon_s3.md b/manual/deploy_pro/setup_with_amazon_s3.md index 88c0d023..780c08b9 100644 --- a/manual/deploy_pro/setup_with_amazon_s3.md +++ b/manual/deploy_pro/setup_with_amazon_s3.md @@ -42,7 +42,7 @@ key_id = your-key-id key = your-secret-key ``` -You also need to add [memory cache configurations](/config/seafile-conf.md#cache-pro-edition-only). +You also need to add [memory cache configurations](/config/seafile-conf/#cache-pro-edition-only). It's required to create separate buckets for commit, fs, and block objects. The key_id and key are required to authenticate you to S3. You can find the key_id and key in the "security credentials" section on your AWS account page. @@ -162,7 +162,7 @@ path_style_request = true `path_style_request` asks Seafile to use URLs like `https://192.168.1.123:8080/bucketname/object` to access objects. In Amazon S3, the default URL format is in virtual host style, such as `https://bucketname.s3.amazonaws.com/object`. But this style relies on advanced DNS server setup. So most S3-compatible storage systems only implement the path style format. -You also need to add [memory cache configurations](/config/seafile-conf.md#cache-pro-edition-only). +You also need to add [memory cache configurations](/config/seafile-conf/#cache-pro-edition-only). ## Run and Test ## diff --git a/manual/deploy_pro/setup_with_ceph.md b/manual/deploy_pro/setup_with_ceph.md index 477e79e2..eed8dfa8 100644 --- a/manual/deploy_pro/setup_with_ceph.md +++ b/manual/deploy_pro/setup_with_ceph.md @@ -63,7 +63,7 @@ ceph_config = /etc/ceph/ceph.conf pool = seafile-fs ``` -You also need to add [memory cache configurations](/manual/config/seafile-conf/#cache-pro-edition-only). +You also need to add [memory cache configurations](/config/seafile-conf/#cache-pro-edition-only). It's required to create separate pools for commit, fs, and block objects. diff --git a/manual/deploy_pro/setup_with_oss.md b/manual/deploy_pro/setup_with_oss.md index 56783b76..ece4652a 100644 --- a/manual/deploy_pro/setup_with_oss.md +++ b/manual/deploy_pro/setup_with_oss.md @@ -34,7 +34,7 @@ key = region = beijing ``` -You also need to add [memory cache configurations](/manual/config/seafile-conf/#cache-pro-edition-only). +You also need to add [memory cache configurations](/config/seafile-conf/#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. @@ -76,4 +76,4 @@ Compared with the configuration under the classic network, the above configurati `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. -You also need to add [memory cache configurations](/manual/config/seafile-conf/#cache-pro-edition-only). +You also need to add [memory cache configurations](/config/seafile-conf/#cache-pro-edition-only). diff --git a/manual/deploy_pro/setup_with_swift.md b/manual/deploy_pro/setup_with_swift.md index b18425c4..f987595e 100644 --- a/manual/deploy_pro/setup_with_swift.md +++ b/manual/deploy_pro/setup_with_swift.md @@ -48,7 +48,7 @@ region = yourRegion ``` -You also need to add [memory cache configurations](/manual/config/seafile-conf/#cache-pro-edition-only). +You also need to add [memory cache configurations](/config/seafile-conf/#cache-pro-edition-only). The above config is just an example. You should replace the options according to your own environment.