-
Notifications
You must be signed in to change notification settings - Fork 709
v6.1: update download URL from pingcap.org to pingcap.com #22242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: release-6.1
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -31,12 +31,12 @@ Download a new installation package from the [Prometheus download page](https:// | |||||
| 1. Download the TiDB server package and extract it. Note that your downloading means you agree to the [Privacy Policy](https://www.pingcap.com/privacy-policy/). | ||||||
|
|
||||||
| ``` | ||||||
| https://download.pingcap.org/tidb-community-server-{version}-linux-{arch}.tar.gz | ||||||
| https://download.pingcap.com/tidb-community-server-{version}-linux-{arch}.tar.gz | ||||||
| ``` | ||||||
|
|
||||||
| > **Tip:** | ||||||
| > | ||||||
| > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v6.1.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v6.1.0-linux-amd64.tar.gz`. | ||||||
| > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v6.1.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v6.1.0-linux-amd64.tar.gz`. | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The example download link refers to
Suggested change
|
||||||
|
|
||||||
| 2. In the extracted files, locate `prometheus-v{version}-linux-amd64.tar.gz` and extract it. | ||||||
|
|
||||||
|
|
@@ -80,12 +80,12 @@ In the following upgrade steps, you need to download the Grafana installation pa | |||||
| 1. Download the TiDB server package and extract it. Note that your downloading means you agree to the [Privacy Policy](https://www.pingcap.com/privacy-policy/). | ||||||
|
|
||||||
| ``` | ||||||
| https://download.pingcap.org/tidb-community-server-{version}-linux-{arch}.tar.gz | ||||||
| https://download.pingcap.com/tidb-community-server-{version}-linux-{arch}.tar.gz | ||||||
| ``` | ||||||
|
|
||||||
| > **Tip:** | ||||||
| > | ||||||
| > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v6.1.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v6.1.0-linux-amd64.tar.gz`. | ||||||
| > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v6.1.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v6.1.0-linux-amd64.tar.gz`. | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Similar to the previous section, the example download link here refers to
Suggested change
|
||||||
|
|
||||||
| 2. In the extracted files, locate `grafana-v{version}-linux-amd64.tar.gz` and extract it. | ||||||
|
|
||||||
|
|
||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The command in the example output is inconsistent with the command provided above it (line 45). Also, the use of
curl -LO ... | tar ...is incorrect because the-Oflag saves the output to a file instead of stdout, leaving nothing fortarto read from the pipe. To maintain consistency and correctness, I suggest updating the command in the example output to match the one on line 45.