From 879ca011b05f70e3e06c71cc0ec7672f000d69eb Mon Sep 17 00:00:00 2001 From: zhaoxinxin <1186037180@qq.com> Date: Thu, 5 Dec 2024 20:49:46 +0800 Subject: [PATCH] docs: change binaries deb and rpm Signed-off-by: zhaoxinxin <1186037180@qq.com> --- docs/advanced-guides/preheat.md | 2 +- .../configure-development-nvironment.md | 8 ++++---- docs/getting-started/installation/binaries.md | 14 +++++++------- .../best-practices/deployment-best-practices.md | 14 +++++++------- .../integrations/container-runtime/containerd.md | 6 +++--- .../integrations/container-runtime/cri-o.md | 6 +++--- .../integrations/container-runtime/podman.md | 6 +++--- 7 files changed, 28 insertions(+), 28 deletions(-) diff --git a/docs/advanced-guides/preheat.md b/docs/advanced-guides/preheat.md index 6175b83..200aca3 100644 --- a/docs/advanced-guides/preheat.md +++ b/docs/advanced-guides/preheat.md @@ -278,7 +278,7 @@ To support preheating for harbor with self-signed certificates, the Manager configuration needs to be modified. Configure `manager.yaml`, the default path is `/etc/dragonfly/manager.yaml`, -refer to [Manager](../reference/configuration/manager.md). +refer to [manager config](../reference/configuration/manager.md). > Notice: `yourdomain.crt` is Harbor's ca.crt. diff --git a/docs/development-guide/configure-development-nvironment.md b/docs/development-guide/configure-development-nvironment.md index 0574b09..2c57177 100644 --- a/docs/development-guide/configure-development-nvironment.md +++ b/docs/development-guide/configure-development-nvironment.md @@ -43,7 +43,7 @@ cd client #### Setup Manager {#setup-manager} Configure `manager.yaml`, the default path is `/etc/dragonfly/manager.yaml`, -refer to [manager.yaml](../reference/configuration/manager.md). +refer to [manager config](../reference/configuration/manager.md). Set the `database.mysql.addrs` and `database.redis.addrs` address in the configuration file to your actual address. Configuration content is as follows: @@ -94,7 +94,7 @@ telnet 127.0.0.1 65003 #### Setup Scheduler {#setup-scheduler} Configure `scheduler.yaml`, the default path is `/etc/dragonfly/scheduler.yaml`, -refer to [scheduler.yaml](../reference/configuration/scheduler.md). +refer to [scheduler config](../reference/configuration/scheduler.md). Set the `database.redis.addrs` and `manager.addr` address in the configuration file to your actual address. Configuration content is as follows: @@ -140,7 +140,7 @@ telnet 127.0.0.1 8002 #### Setup Dfdaemon as Seed Peer {#setup-dfdaemon-as-seed-peer} Configure `dfdaemon.yaml`, the default path is `/etc/dragonfly/dfdaemon.yaml`, -refer to [dfdaemon.yaml](../reference/configuration/client/dfdaemon.md). +refer to [dfdaemon config](../reference/configuration/client/dfdaemon.md). Set the `manager.addrs` address in the configuration file to your actual address. Configuration content is as follows: @@ -178,7 +178,7 @@ telnet 127.0.0.1 4002 #### Setup Dfdaemon as Peer {#setup-dfdaemon-as-Peer} Configure `dfdaemon.yaml`, the default path is `/etc/dragonfly/dfdaemon.yaml`, -refer to [dfdaemon.yaml](../reference/configuration/client/dfdaemon.md). +refer to [dfdaemon config](../reference/configuration/client/dfdaemon.md). Set the `manager.addrs` address in the configuration file to your actual address. Configuration content is as follows: diff --git a/docs/getting-started/installation/binaries.md b/docs/getting-started/installation/binaries.md index bbc032a..679ca81 100644 --- a/docs/getting-started/installation/binaries.md +++ b/docs/getting-started/installation/binaries.md @@ -137,9 +137,9 @@ Make sure to replace `arch` with one of the following: #### Step 2: Configure dfdaemon {#configure-dfdaemon-rpm} -Create the Dfdaemon configuration file `/etc/dragonfly/dfdaemon.yaml` +Create the dfdaemon configuration file `/etc/dragonfly/dfdaemon.yaml` and modify the `manager.addrs` in the configuration file to your actual address. -Refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +Refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). ##### Option 1: Setup Dfdaemon as Seed Peer {#setup-dfdaemon-as-seed-peer-rpm} @@ -220,7 +220,7 @@ Make sure to replace `arch` with one of the following: Create the dfdaemon configuration file `/etc/dragonfly/dfdaemon.yaml` and modify the `manager.addrs` in the configuration file to your actual address. -Refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +Refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). ##### Option 1: Setup Dfdaemon as Seed Peer {#setup-dfdaemon-as-seed-peer-deb} @@ -283,7 +283,7 @@ dfget -O /path/to/output http://example.com/object #### Setup Manager {#setup-manager} Configure `manager.yaml`, the default path is `/etc/dragonfly/manager.yaml`, -refer to [manager.yaml](../../reference/configuration/manager.md). +refer to [manager config](../../reference/configuration/manager.md). Set the `database.mysql.addrs` and `database.redis.addrs` address in the configuration file to your actual address. Configuration content is as follows: @@ -341,7 +341,7 @@ Now you can open brower and visit console by localhost:8080, Console features pr #### Setup Scheduler {#setup-scheduler} Configure `scheduler.yaml`, the default path is `/etc/dragonfly/scheduler.yaml`, -refer to [scheduler.yaml](../../reference/configuration/scheduler.md). +refer to [scheduler config](../../reference/configuration/scheduler.md). Set the `database.redis.addrs` and `manager.addr` address in the configuration file to your actual address. Configuration content is as follows: @@ -388,7 +388,7 @@ telnet 127.0.0.1 8002 #### Setup Dfdaemon as Seed Peer {#setup-dfdaemon-as-seed-peer} Configure `dfdaemon.yaml`, the default path is `/etc/dragonfly/dfdaemon.yaml`, -refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). Set the `manager.addrs` address in the configuration file to your actual address. Configuration content is as follows: @@ -427,7 +427,7 @@ telnet 127.0.0.1 4002 #### Setup Dfdaemon as Peer {#setup-dfdaemon-as-Peer} Configure `dfdaemon.yaml`, the default path is `/etc/dragonfly/dfdaemon.yaml`, -refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). Set the `manager.addrs` address in the configuration file to your actual address. Configuration content is as follows: diff --git a/docs/operations/best-practices/deployment-best-practices.md b/docs/operations/best-practices/deployment-best-practices.md index b3228a5..a6717ac 100644 --- a/docs/operations/best-practices/deployment-best-practices.md +++ b/docs/operations/best-practices/deployment-best-practices.md @@ -89,7 +89,7 @@ Used for node P2P to share piece bandwidth. If the peak bandwidth is greater than the default outbound bandwidth, you can set `rateLimit` higher to increase the upload speed. It is recommended that the configuration be the same as the inbound bandwidth of the machine. -Please refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +Please refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). ```yaml upload: @@ -103,7 +103,7 @@ Used for node back-to-source bandwidth and download bandwidth from remote peer. If the peak bandwidth is greater than the default inbound bandwidth, `rateLimit` can be set higher to increase download speed. It is recommended that the configuration be the same as the outbound bandwidth of the machine. -Please refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +Please refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). ```yaml download: @@ -118,7 +118,7 @@ the number of concurrent downloads of piece back-to-source and the number of con The larger the number of piece concurrency, the faster the task download, and the more CPU and memory will be consumed. The user adjusts the number of piece concurrency according to the actual situation. and adjust the client’s CPU and memory configuration. -Please refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +Please refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). ```yaml download: @@ -131,7 +131,7 @@ download: Used for task cache GC in node disk, taskTTL is calculated based on cache time. To avoid cases where GC would be problematic or potentially catastrophi, it is recommended to use the default value. -Please refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +Please refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). ```yaml gc: @@ -158,7 +158,7 @@ When Dragonfly is used as a cache service for Nydus, the configuration needs to **1.** `proxy.rules.regex` matches the Nydus repository URL, intercepts download traffic and forwards it to the P2P network. -Please refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +Please refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). ```yaml proxy: @@ -192,7 +192,7 @@ Changed `Seed Peer Load Limit` successfully. **3.** Nydus will initiate an HTTP range request of about 1MB to achieve on-demand loading. When prefetch enabled, the Seed Peer can prefetch the complete resource after receiving the HTTP range request, improving the cache hit rate. -Please refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +Please refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). ```yaml proxy: @@ -202,7 +202,7 @@ proxy: **4.** When the download speed is slow, you can adjust the `readBufferSize` value of proxy to 64KB in order to reduce the proxy request time. -Please refer to [dfdaemon.yaml](../../reference/configuration/client/dfdaemon.md). +Please refer to [dfdaemon config](../../reference/configuration/client/dfdaemon.md). ```yaml proxy: diff --git a/docs/operations/integrations/container-runtime/containerd.md b/docs/operations/integrations/container-runtime/containerd.md index 0e88824..9307da3 100644 --- a/docs/operations/integrations/container-runtime/containerd.md +++ b/docs/operations/integrations/container-runtime/containerd.md @@ -576,7 +576,7 @@ Install Dragonfly with Binaries, refer to [Binaries](../../../getting-started/in To support preheating for harbor with self-signed certificates, the Manager configuration needs to be modified. Configure `manager.yaml`, the default path is `/etc/dragonfly/manager.yaml`, -refer to [manager.yaml](../../../reference/configuration/manager.md). +refer to [manager config](../../../reference/configuration/manager.md). > Notice: `yourdomain.crt` is Harbor's ca.crt. @@ -607,7 +607,7 @@ job: ##### Setup Dfdaemon as Seed Peer and configure self-signed certificate Configure `dfdaemon.yaml`, the default path is `/etc/dragonfly/dfdaemon.yaml`, -refer to [dfdaemon.yaml](../../../reference/configuration/client/dfdaemon.md). +refer to [dfdaemon config](../../../reference/configuration/client/dfdaemon.md). ```shell manager: @@ -632,7 +632,7 @@ proxy: ##### Setup Dfdaemon as Peer and configure self-signed certificate Configure `dfdaemon.yaml`, the default path is `/etc/dragonfly/dfdaemon.yaml`, -refer to [dfdaemon.yaml](../../../reference/configuration/client/dfdaemon.md). +refer to [dfdaemon config](../../../reference/configuration/client/dfdaemon.md). ```shell manager: diff --git a/docs/operations/integrations/container-runtime/cri-o.md b/docs/operations/integrations/container-runtime/cri-o.md index cecc287..a9304ca 100644 --- a/docs/operations/integrations/container-runtime/cri-o.md +++ b/docs/operations/integrations/container-runtime/cri-o.md @@ -379,7 +379,7 @@ Install Dragonfly with Binaries, refer to [Binaries](../../../getting-started/in To support preheating for harbor with self-signed certificates, the Manager configuration needs to be modified. Configure `manager.yaml`, the default path is `/etc/dragonfly/manager.yaml`, -refer to [manager.yaml](../../../reference/configuration/manager.md). +refer to [manager config](../../../reference/configuration/manager.md). > Notice: `yourdomain.crt` is Harbor's ca.crt. @@ -410,7 +410,7 @@ job: ##### Setup Dfdaemon as Seed Peer and configure self-signed certificate Configure `dfdaemon.yaml`, the default path is `/etc/dragonfly/dfdaemon.yaml`, -refer to [dfdaemon.yaml](../../../reference/configuration/client/dfdaemon.md). +refer to [dfdaemon config](../../../reference/configuration/client/dfdaemon.md). ```shell manager: @@ -435,7 +435,7 @@ proxy: ##### Setup Dfdaemon as Peer and configure self-signed certificate Configure `dfdaemon.yaml`, the default path is `/etc/dragonfly/dfdaemon.yaml`, -refer to [dfdaemon.yaml](../../../reference/configuration/client/dfdaemon.md). +refer to [dfdaemon config](../../../reference/configuration/client/dfdaemon.md). ```shell manager: diff --git a/docs/operations/integrations/container-runtime/podman.md b/docs/operations/integrations/container-runtime/podman.md index 9f36bda..a4c92f3 100644 --- a/docs/operations/integrations/container-runtime/podman.md +++ b/docs/operations/integrations/container-runtime/podman.md @@ -379,7 +379,7 @@ Install Dragonfly with Binaries, refer to [Binaries](../../../getting-started/in To support preheating for harbor with self-signed certificates, the Manager configuration needs to be modified. Configure `manager.yaml`, the default path is `/etc/dragonfly/manager.yaml`, -refer to [manager.yaml](../../../reference/configuration/manager.md). +refer to [manager config](../../../reference/configuration/manager.md). > Notice: `yourdomain.crt` is Harbor's ca.crt. @@ -410,7 +410,7 @@ job: ##### Setup Dfdaemon as Seed Peer and configure self-signed certificate Configure `dfdaemon.yaml`, the default path is `/etc/dragonfly/dfdaemon.yaml`, -refer to [dfdaemon.md](../../../reference/configuration/client/dfdaemon.md). +refer to [dfdaemon config](../../../reference/configuration/client/dfdaemon.md). ```shell manager: @@ -435,7 +435,7 @@ proxy: ##### Setup Dfdaemon as Peer and configure self-signed certificate Configure `dfdaemon.yaml`, the default path is `/etc/dragonfly/dfdaemon.yaml`, -refer to [dfdaemon.md](../../../reference/configuration/client/dfdaemon.md). +refer to [dfdaemon config](../../../reference/configuration/client/dfdaemon.md). ```shell manager: