From 0089cffb8e04cf9ba933540dc84058ded4be54aa Mon Sep 17 00:00:00 2001 From: yikeke Date: Wed, 8 Jan 2020 10:49:58 +0800 Subject: [PATCH] *: change http to https --- dev/how-to/deploy/data-migration-with-ansible.md | 4 ++-- .../from-tarball/production-environment.md | 4 ++-- .../deploy/from-tarball/testing-environment.md | 4 ++-- dev/how-to/get-started/data-migration.md | 4 ++-- .../get-started/deploy-tidb-from-binary.md | 4 ++-- dev/how-to/get-started/tidb-binlog.md | 4 ++-- dev/how-to/get-started/tidb-lightning.md | 2 +- .../backup-and-restore/mydumper-loader.md | 4 ++-- dev/reference/tidb-binlog/reparo.md | 2 +- dev/reference/tidb-binlog/tidb-binlog-kafka.md | 8 ++++---- dev/reference/tools/download.md | 16 ++++++++-------- dev/reference/tools/pd-control.md | 4 ++-- scripts/upload.py | 2 +- v1.0/op-guide/ansible-deployment.md | 2 +- v1.0/op-guide/backup-restore.md | 4 ++-- v1.0/op-guide/binary-deployment.md | 4 ++-- v1.0/op-guide/migration-overview.md | 4 ++-- v1.0/op-guide/migration.md | 4 ++-- v1.0/op-guide/offline-ansible-deployment.md | 2 +- v1.0/scripts/upload.py | 2 +- v1.0/tispark/tispark-user-guide.md | 2 +- v1.0/tools/loader.md | 2 +- v1.0/tools/syncer.md | 4 ++-- v1.0/tools/tidb-binlog-kafka.md | 8 ++++---- v1.0/tools/tidb-binlog.md | 4 ++-- .../ansible-deployment-rolling-update.md | 2 +- v2.0/op-guide/backup-restore.md | 4 ++-- v2.0/op-guide/migration-overview.md | 4 ++-- v2.0/op-guide/migration.md | 4 ++-- v2.0/scripts/upload.py | 2 +- v2.0/tikv/deploy-tikv-using-binary.md | 4 ++-- v2.0/tispark/tispark-user-guide.md | 2 +- v2.0/tools/loader.md | 2 +- v2.0/tools/syncer.md | 4 ++-- v2.0/tools/tidb-binlog-kafka.md | 8 ++++---- v2.0/tools/tidb-binlog.md | 4 ++-- .../ansible-deployment-rolling-update.md | 4 ++-- v2.1-legacy/op-guide/backup-restore.md | 4 ++-- v2.1-legacy/op-guide/migration-overview.md | 4 ++-- v2.1-legacy/op-guide/migration.md | 4 ++-- v2.1-legacy/scripts/upload.py | 2 +- v2.1-legacy/tikv/deploy-tikv-using-binary.md | 4 ++-- v2.1-legacy/tispark/tispark-user-guide.md | 2 +- v2.1-legacy/tools/data-migration-deployment.md | 4 ++-- v2.1-legacy/tools/loader.md | 2 +- v2.1-legacy/tools/mydumper.md | 2 +- v2.1-legacy/tools/syncer.md | 4 ++-- v2.1-legacy/tools/tidb-binlog-kafka.md | 8 ++++---- v2.1-legacy/tools/tidb-binlog.md | 4 ++-- .../how-to/deploy/data-migration-with-ansible.md | 4 ++-- .../from-tarball/production-environment.md | 4 ++-- .../deploy/from-tarball/testing-environment.md | 4 ++-- v2.1/how-to/get-started/data-migration.md | 4 ++-- .../get-started/deploy-tidb-from-binary.md | 4 ++-- v2.1/how-to/get-started/tidb-binlog.md | 4 ++-- v2.1/how-to/get-started/tidb-lightning.md | 2 +- v2.1/how-to/maintain/backup-and-restore.md | 4 ++-- v2.1/reference/tidb-binlog/reparo.md | 2 +- v2.1/reference/tidb-binlog/tidb-binlog-kafka.md | 8 ++++---- v2.1/reference/tispark.md | 2 +- v2.1/reference/tools/download.md | 16 ++++++++-------- v2.1/reference/tools/pd-control.md | 4 ++-- v2.1/tispark/tispark-user-guide_v1.x.md | 2 +- .../how-to/deploy/data-migration-with-ansible.md | 4 ++-- .../from-tarball/production-environment.md | 2 +- .../deploy/from-tarball/testing-environment.md | 2 +- v3.0/how-to/get-started/data-migration.md | 4 ++-- .../get-started/deploy-tidb-from-binary.md | 2 +- v3.0/how-to/get-started/tidb-binlog.md | 4 ++-- v3.0/how-to/get-started/tidb-lightning.md | 2 +- v3.0/how-to/maintain/backup-and-restore.md | 4 ++-- v3.0/reference/tidb-binlog/reparo.md | 2 +- v3.0/reference/tidb-binlog/tidb-binlog-kafka.md | 8 ++++---- v3.0/reference/tools/download.md | 16 ++++++++-------- v3.0/reference/tools/pd-control.md | 4 ++-- .../how-to/deploy/data-migration-with-ansible.md | 4 ++-- .../from-tarball/production-environment.md | 2 +- .../deploy/from-tarball/testing-environment.md | 2 +- v3.1/how-to/get-started/data-migration.md | 4 ++-- .../get-started/deploy-tidb-from-binary.md | 2 +- v3.1/how-to/get-started/tidb-binlog.md | 4 ++-- v3.1/how-to/get-started/tidb-lightning.md | 2 +- .../backup-and-restore/mydumper-loader.md | 4 ++-- v3.1/reference/tidb-binlog/reparo.md | 2 +- v3.1/reference/tidb-binlog/tidb-binlog-kafka.md | 8 ++++---- v3.1/reference/tools/download.md | 16 ++++++++-------- v3.1/reference/tools/pd-control.md | 4 ++-- 87 files changed, 182 insertions(+), 182 deletions(-) diff --git a/dev/how-to/deploy/data-migration-with-ansible.md b/dev/how-to/deploy/data-migration-with-ansible.md index b0febc72f2550..bb909842a1adb 100644 --- a/dev/how-to/deploy/data-migration-with-ansible.md +++ b/dev/how-to/deploy/data-migration-with-ansible.md @@ -112,7 +112,7 @@ Make sure you have logged in to the Control Machine using the `tidb` user accoun 2. Run the following command to download DM-Ansible. ```bash - $ wget http://download.pingcap.org/dm-ansible-{version}.tar.gz + $ wget https://download.pingcap.org/dm-ansible-{version}.tar.gz ``` `{version}` is the DM version that you expect to download, like `v1.0.1` and `v1.0.2`. @@ -465,7 +465,7 @@ dm_master ansible_host=172.16.10.71 dm_master_port=18261 ``` $ cd /home/tidb - $ wget http://download.pingcap.org/dm-ansible-{version}.tar.gz + $ wget https://download.pingcap.org/dm-ansible-{version}.tar.gz $ tar -xzvf dm-ansible-{version}.tar.gz $ mv dm-ansible-{version} dm-ansible ``` diff --git a/dev/how-to/deploy/from-tarball/production-environment.md b/dev/how-to/deploy/from-tarball/production-environment.md index ed2617a400417..067efe6613e12 100644 --- a/dev/how-to/deploy/from-tarball/production-environment.md +++ b/dev/how-to/deploy/from-tarball/production-environment.md @@ -106,8 +106,8 @@ See the following table for the default ports for the optional TiDB components: ``` # Download the package. -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-latest-linux-amd64.sha256 diff --git a/dev/how-to/deploy/from-tarball/testing-environment.md b/dev/how-to/deploy/from-tarball/testing-environment.md index fbd53407116df..b90bdccf79493 100644 --- a/dev/how-to/deploy/from-tarball/testing-environment.md +++ b/dev/how-to/deploy/from-tarball/testing-environment.md @@ -106,8 +106,8 @@ See the following table for the default ports for the optional TiDB components: ``` # Download the package. -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-latest-linux-amd64.sha256 diff --git a/dev/how-to/get-started/data-migration.md b/dev/how-to/get-started/data-migration.md index 0b8b2e8b3f1f4..2dd7914f29687 100644 --- a/dev/how-to/get-started/data-migration.md +++ b/dev/how-to/get-started/data-migration.md @@ -41,8 +41,8 @@ We're going to deploy 3 instances of MySQL Server, and 1 instance each of pd-ser ```bash sudo yum install -y http://repo.mysql.com/yum/mysql-5.7-community/el/7/x86_64/mysql57-community-release-el7-10.noarch.rpm sudo yum install -y mysql-community-server - curl http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - - curl http://download.pingcap.org/dm-v1.0.2-linux-amd64.tar.gz | tar xzf - + curl https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - + curl https://download.pingcap.org/dm-v1.0.2-linux-amd64.tar.gz | tar xzf - curl -L https://github.com/pingcap/docs/raw/master/dev/how-to/get-started/dm-cnf/dm-cnf.tgz | tar xvzf - ``` diff --git a/dev/how-to/get-started/deploy-tidb-from-binary.md b/dev/how-to/get-started/deploy-tidb-from-binary.md index fde0aec1700c8..3ecc344876833 100644 --- a/dev/how-to/get-started/deploy-tidb-from-binary.md +++ b/dev/how-to/get-started/deploy-tidb-from-binary.md @@ -56,8 +56,8 @@ See the [production deployment](/dev/how-to/deploy/from-tarball/production-envir ``` # Download the package. -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-latest-linux-amd64.sha256 diff --git a/dev/how-to/get-started/tidb-binlog.md b/dev/how-to/get-started/tidb-binlog.md index a114686234813..0eda120747b3f 100644 --- a/dev/how-to/get-started/tidb-binlog.md +++ b/dev/how-to/get-started/tidb-binlog.md @@ -45,14 +45,14 @@ sudo yum install -y mariadb-server Even if you've already started a TiDB cluster, it will be easier to follow along with this tutorial where we will set up a new, simple cluster. We will install from a tarball, using a simplified form of the [Local Deployment](/dev/how-to/get-started/deploy-tidb-from-binary.md) guide. You may also wish to refer to [Testing Deployment from Binary Tarball](/dev/how-to/deploy/from-tarball/testing-environment.md) for best practices of establishing a real testing deployment, but that goes beyond the scope of this tutorial. ```bash -curl -L http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz | tar xzf - +curl -L https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz | tar xzf - cd tidb-latest-linux-amd64 ``` Expected output: ``` -[kolbe@localhost ~]$ curl -LO http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz | tar xzf - +[kolbe@localhost ~]$ curl -LO https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz | tar xzf - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 368M 100 368M 0 0 8394k 0 0:00:44 0:00:44 --:--:-- 11.1M diff --git a/dev/how-to/get-started/tidb-lightning.md b/dev/how-to/get-started/tidb-lightning.md index 359bd295ee0de..d144a62172c2f 100644 --- a/dev/how-to/get-started/tidb-lightning.md +++ b/dev/how-to/get-started/tidb-lightning.md @@ -57,7 +57,7 @@ Before the data import, you need to deploy a TiDB cluster (later than v2.0.9). I Download the TiDB Lightning installation package from the following link: -- **v3.0.4**: [tidb-toolkit-v3.0.4-linux-amd64.tar.gz](http://download.pingcap.org/tidb-toolkit-v3.0.0-linux-amd64.tar.gz) +- **v3.0.4**: [tidb-toolkit-v3.0.4-linux-amd64.tar.gz](https://download.pingcap.org/tidb-toolkit-v3.0.0-linux-amd64.tar.gz) > **Note:** > diff --git a/dev/how-to/maintain/backup-and-restore/mydumper-loader.md b/dev/how-to/maintain/backup-and-restore/mydumper-loader.md index b7a799841ea55..7e3ab1659f74c 100644 --- a/dev/how-to/maintain/backup-and-restore/mydumper-loader.md +++ b/dev/how-to/maintain/backup-and-restore/mydumper-loader.md @@ -27,8 +27,8 @@ Use the following tools for data backup and restoration: {{< copyable "shell-regular" >}} ```bash - wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz && \ - wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 + wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz && \ + wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 ``` 2. Check the file integrity. If the result is fine, the file is correct. diff --git a/dev/reference/tidb-binlog/reparo.md b/dev/reference/tidb-binlog/reparo.md index d99e91a35085d..8809715c20393 100644 --- a/dev/reference/tidb-binlog/reparo.md +++ b/dev/reference/tidb-binlog/reparo.md @@ -8,7 +8,7 @@ category: reference Reparo is a TiDB Binlog tool, used to recover the incremental data. To back up the incremental data, you can use Drainer of TiDB Binlog to output the binlog data in the protobuf format to files. To restore the incremental data, you can use Reparo to parse the binlog data in the files and apply the binlog in TiDB/MySQL. -Download Reparo via [tidb-binlog-cluster-latest-linux-amd64.tar.gz](http://download.pingcap.org/tidb-binlog-cluster-latest-linux-amd64.tar.gz) +Download Reparo via [tidb-binlog-cluster-latest-linux-amd64.tar.gz](https://download.pingcap.org/tidb-binlog-cluster-latest-linux-amd64.tar.gz) ## Reparo usage diff --git a/dev/reference/tidb-binlog/tidb-binlog-kafka.md b/dev/reference/tidb-binlog/tidb-binlog-kafka.md index cdadcb845c75b..e12520cd61ceb 100644 --- a/dev/reference/tidb-binlog/tidb-binlog-kafka.md +++ b/dev/reference/tidb-binlog/tidb-binlog-kafka.md @@ -53,8 +53,8 @@ The corresponding relationship between the `tidb-ansible` branch and the TiDB ve ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-binlog-kafka-linux-amd64.sha256 @@ -382,8 +382,8 @@ CentOS 7+ ```bash # Download PbReader package -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c pb_reader-latest-linux-amd64.sha256 diff --git a/dev/reference/tools/download.md b/dev/reference/tools/download.md index 581c72a775fa6..9f6cffcdd8e53 100644 --- a/dev/reference/tools/download.md +++ b/dev/reference/tools/download.md @@ -16,12 +16,12 @@ In addition, the Kafka version of TiDB Binlog is also provided. | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (TiDB Binlog) | Linux | amd64 | `http://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | -| `http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz` (the Kafka version of TiDB Binlog) | Linux | amd64 | `http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (TiDB Binlog) | Linux | amd64 | `https://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz` (the Kafka version of TiDB Binlog) | Linux | amd64 | `https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v3.0.5` is `http://download.pingcap.org/tidb-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v3.0.5` is `https://download.pingcap.org/tidb-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## TiDB Lightning @@ -29,11 +29,11 @@ Download [TiDB Lightning](/dev/reference/tools/tidb-lightning/overview.md) by us | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.tar.gz` | Linux | amd64 | `http://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.tar.gz` | Linux | amd64 | `https://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v3.0.5` is `http://download.pingcap.org/tidb-toolkit-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v3.0.5` is `https://download.pingcap.org/tidb-toolkit-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## TiDB DM (Data Migration) @@ -41,11 +41,11 @@ Download [DM](/dev/reference/tools/data-migration/overview.md) by using the down | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/dm-{version}-linux-amd64.tar.gz` | Linux | amd64 | `http://download.pingcap.org/dm-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/dm-{version}-linux-amd64.tar.gz` | Linux | amd64 | `https://download.pingcap.org/dm-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v1.0.1` is `http://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v1.0.1` is `https://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## Syncer, Loader, and Mydumper @@ -53,7 +53,7 @@ If you want to download the latest version of [Syncer](/dev/reference/tools/sync | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| [tidb-enterprise-tools-latest-linux-amd64.tar.gz](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz) | Linux | amd64 | [tidb-enterprise-tools-latest-linux-amd64.sha256](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256) | +| [tidb-enterprise-tools-latest-linux-amd64.tar.gz](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz) | Linux | amd64 | [tidb-enterprise-tools-latest-linux-amd64.sha256](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256) | This enterprise tools package includes all the following tools: diff --git a/dev/reference/tools/pd-control.md b/dev/reference/tools/pd-control.md index 77b07bca004ac..c76170a623449 100644 --- a/dev/reference/tools/pd-control.md +++ b/dev/reference/tools/pd-control.md @@ -23,11 +23,11 @@ If you want to download the latest version of `pd-ctl`, directly download the Ti | Package download link | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `http://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `https://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v3.0.7`, the package download link is `http://download.pingcap.org/tidb-v3.0.7-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v3.0.7`, the package download link is `https://download.pingcap.org/tidb-v3.0.7-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## Usage diff --git a/scripts/upload.py b/scripts/upload.py index 961a68bdc847e..36b0e479e12b4 100755 --- a/scripts/upload.py +++ b/scripts/upload.py @@ -44,4 +44,4 @@ def upload(local_file, remote_name, ttl=3600): print(local_file, remote_name) upload(local_file, remote_name) - print("http://download.pingcap.org/{}".format(remote_name)) + print("https://download.pingcap.org/{}".format(remote_name)) diff --git a/v1.0/op-guide/ansible-deployment.md b/v1.0/op-guide/ansible-deployment.md index 72911c1693387..884565baad0d6 100755 --- a/v1.0/op-guide/ansible-deployment.md +++ b/v1.0/op-guide/ansible-deployment.md @@ -366,7 +366,7 @@ It is recommended to configure load balancing to provide uniform SQL interface. You can also download the binary manually. Use `wget` to download the binary and replace the existing binary in `tidb-ansible/resource/bin/` manually. ``` -wget http://download.pingcap.org/tidb-v1.0.0-linux-amd64-unportable.tar.gz +wget https://download.pingcap.org/tidb-v1.0.0-linux-amd64-unportable.tar.gz ``` > **Note:** diff --git a/v1.0/op-guide/backup-restore.md b/v1.0/op-guide/backup-restore.md index 251e5a205eeb0..405326b016c9b 100755 --- a/v1.0/op-guide/backup-restore.md +++ b/v1.0/op-guide/backup-restore.md @@ -24,8 +24,8 @@ Use the following tools for data backup and restoration: ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v1.0/op-guide/binary-deployment.md b/v1.0/op-guide/binary-deployment.md index bc1d3dea2016a..416d9f6cc700d 100755 --- a/v1.0/op-guide/binary-deployment.md +++ b/v1.0/op-guide/binary-deployment.md @@ -138,8 +138,8 @@ TiDB provides the official binary installation package that supports Linux. For ``` # Download the package. -wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-latest-linux-amd64.sha256 diff --git a/v1.0/op-guide/migration-overview.md b/v1.0/op-guide/migration-overview.md index b38d19ea42edc..98955f96ecf5b 100755 --- a/v1.0/op-guide/migration-overview.md +++ b/v1.0/op-guide/migration-overview.md @@ -54,8 +54,8 @@ See [Download the TiDB toolset](#download-the-tidb-toolset-linux) to download th ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v1.0/op-guide/migration.md b/v1.0/op-guide/migration.md index 63f3564fdb783..3031c48b9720b 100755 --- a/v1.0/op-guide/migration.md +++ b/v1.0/op-guide/migration.md @@ -108,8 +108,8 @@ See [Download the TiDB enterprise toolset](#download-the-tidb-enterprise-toolset ```bash # Download the enterprise tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v1.0/op-guide/offline-ansible-deployment.md b/v1.0/op-guide/offline-ansible-deployment.md index 11ffc25824fba..fe430b63acf0d 100755 --- a/v1.0/op-guide/offline-ansible-deployment.md +++ b/v1.0/op-guide/offline-ansible-deployment.md @@ -23,7 +23,7 @@ Before you start, make sure that you have: 1. Install Ansible offline on the CentOS 7 system: - > Download the [Ansible](http://download.pingcap.org/ansible-2.4-rpms.el7.tar.gz) offline installation package to the Control Machine. + > Download the [Ansible](https://download.pingcap.org/ansible-2.4-rpms.el7.tar.gz) offline installation package to the Control Machine. ```bash # tar -xzvf ansible-2.4-rpms.el7.tar.gz diff --git a/v1.0/scripts/upload.py b/v1.0/scripts/upload.py index d43a1042c5fb3..6aa6cce99b506 100755 --- a/v1.0/scripts/upload.py +++ b/v1.0/scripts/upload.py @@ -36,4 +36,4 @@ def upload(local_file, remote_name, ttl=3600): remote_name = sys.argv[2] upload(local_file, remote_name) - print("http://download.pingcap.org/{}".format(remote_name)) + print("https://download.pingcap.org/{}".format(remote_name)) diff --git a/v1.0/tispark/tispark-user-guide.md b/v1.0/tispark/tispark-user-guide.md index ca1596be77b26..a2ee8195206fb 100755 --- a/v1.0/tispark/tispark-user-guide.md +++ b/v1.0/tispark/tispark-user-guide.md @@ -92,7 +92,7 @@ For the hybrid deployment of the TiDB Connector for Spark and TiKV, add the TiDB ## Deploy the TiDB Connector for Spark -Download the TiDB Connector for Spark's jar package [here](http://download.pingcap.org/tispark-0.1.0-SNAPSHOT-jar-with-dependencies.jar). +Download the TiDB Connector for Spark's jar package [here](https://download.pingcap.org/tispark-0.1.0-SNAPSHOT-jar-with-dependencies.jar). ### Deploy the TiDB Connector for Spark on the existing Spark cluster diff --git a/v1.0/tools/loader.md b/v1.0/tools/loader.md index 9762717f2f672..91e0ef20f6c45 100755 --- a/v1.0/tools/loader.md +++ b/v1.0/tools/loader.md @@ -9,7 +9,7 @@ category: advanced Loader is a data import tool to load data to TiDB. -[Download the Binary](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz). +[Download the Binary](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz). ## Why did we develop Loader? diff --git a/v1.0/tools/syncer.md b/v1.0/tools/syncer.md index dd50093aecad2..bae16f969885c 100755 --- a/v1.0/tools/syncer.md +++ b/v1.0/tools/syncer.md @@ -17,8 +17,8 @@ Syncer is a tool used to import data incrementally. It is a part of the TiDB ent ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v1.0/tools/tidb-binlog-kafka.md b/v1.0/tools/tidb-binlog-kafka.md index f7cc0c558d209..53f81137a167d 100755 --- a/v1.0/tools/tidb-binlog-kafka.md +++ b/v1.0/tools/tidb-binlog-kafka.md @@ -46,8 +46,8 @@ The Kafka cluster stores the binlog data written by Pump and provides the binlog ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-binlog-latest-linux-amd64.sha256 @@ -351,8 +351,8 @@ CentOS 7+ ```bash # Download PbReader package -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c pb_reader-latest-linux-amd64.sha256 diff --git a/v1.0/tools/tidb-binlog.md b/v1.0/tools/tidb-binlog.md index 14ab578548c81..9955c54bb2e16 100755 --- a/v1.0/tools/tidb-binlog.md +++ b/v1.0/tools/tidb-binlog.md @@ -36,8 +36,8 @@ Drainer collects binlog files from each Pump node, converts them into specified ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-binlog-latest-linux-amd64.sha256 diff --git a/v2.0/op-guide/ansible-deployment-rolling-update.md b/v2.0/op-guide/ansible-deployment-rolling-update.md index 3e4500ccfd16b..eb3e6e842050e 100755 --- a/v2.0/op-guide/ansible-deployment-rolling-update.md +++ b/v2.0/op-guide/ansible-deployment-rolling-update.md @@ -46,7 +46,7 @@ When you perform a rolling update for a TiDB cluster, the service is shut down s You can also download the binary manually. Use `wget` to download the binary and replace the existing binary in `/home/tidb/tidb-ansible/resource/bin/` with it manually. ``` -wget http://download.pingcap.org/tidb-v2.0.3-linux-amd64-unportable.tar.gz +wget https://download.pingcap.org/tidb-v2.0.3-linux-amd64-unportable.tar.gz ``` > **Note:** diff --git a/v2.0/op-guide/backup-restore.md b/v2.0/op-guide/backup-restore.md index a62fe67ad4b20..9af6b198b21e7 100755 --- a/v2.0/op-guide/backup-restore.md +++ b/v2.0/op-guide/backup-restore.md @@ -25,8 +25,8 @@ Use the following tools for data backup and restoration: ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v2.0/op-guide/migration-overview.md b/v2.0/op-guide/migration-overview.md index 19c8d04e20484..ec4d61ebdbb3a 100755 --- a/v2.0/op-guide/migration-overview.md +++ b/v2.0/op-guide/migration-overview.md @@ -55,8 +55,8 @@ See [Download the TiDB toolset](#download-the-tidb-toolset-linux) to download th ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v2.0/op-guide/migration.md b/v2.0/op-guide/migration.md index ea38a92f9703e..a975da3c15dde 100755 --- a/v2.0/op-guide/migration.md +++ b/v2.0/op-guide/migration.md @@ -110,8 +110,8 @@ See [Download the TiDB enterprise toolset](#download-the-tidb-enterprise-toolset ```bash # Download the enterprise tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v2.0/scripts/upload.py b/v2.0/scripts/upload.py index d43a1042c5fb3..6aa6cce99b506 100755 --- a/v2.0/scripts/upload.py +++ b/v2.0/scripts/upload.py @@ -36,4 +36,4 @@ def upload(local_file, remote_name, ttl=3600): remote_name = sys.argv[2] upload(local_file, remote_name) - print("http://download.pingcap.org/{}".format(remote_name)) + print("https://download.pingcap.org/{}".format(remote_name)) diff --git a/v2.0/tikv/deploy-tikv-using-binary.md b/v2.0/tikv/deploy-tikv-using-binary.md index 98cad512e2eda..c4500424e260e 100755 --- a/v2.0/tikv/deploy-tikv-using-binary.md +++ b/v2.0/tikv/deploy-tikv-using-binary.md @@ -20,7 +20,7 @@ This section describes how to deploy TiKV on a single machine installed with the ```bash # Download the package. wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz - wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 + wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-latest-linux-amd64.sha256 @@ -90,7 +90,7 @@ To deploy a TiKV cluster with multiple nodes for test, take the following steps: ```bash # Download the package. wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz - wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 + wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-latest-linux-amd64.sha256 diff --git a/v2.0/tispark/tispark-user-guide.md b/v2.0/tispark/tispark-user-guide.md index 68408bd22fb33..513dbea9672b8 100755 --- a/v2.0/tispark/tispark-user-guide.md +++ b/v2.0/tispark/tispark-user-guide.md @@ -91,7 +91,7 @@ For the hybrid deployment of TiKV and TiSpark, add TiSpark required resources to ## Deploy the TiSpark cluster -Download TiSpark's jar package [here](http://download.pingcap.org/tispark-0.1.0-SNAPSHOT-jar-with-dependencies.jar). +Download TiSpark's jar package [here](https://download.pingcap.org/tispark-0.1.0-SNAPSHOT-jar-with-dependencies.jar). ### Deploy TiSpark on the existing Spark cluster diff --git a/v2.0/tools/loader.md b/v2.0/tools/loader.md index d1c5f6282e44b..92dcb3708e42e 100755 --- a/v2.0/tools/loader.md +++ b/v2.0/tools/loader.md @@ -10,7 +10,7 @@ category: advanced Loader is a data import tool to load data to TiDB. -[Download the Binary](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz). +[Download the Binary](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz). ## Why did we develop Loader? diff --git a/v2.0/tools/syncer.md b/v2.0/tools/syncer.md index cb43cd15079b8..37c4623ccaad7 100755 --- a/v2.0/tools/syncer.md +++ b/v2.0/tools/syncer.md @@ -18,8 +18,8 @@ Syncer is a tool used to import data incrementally. It is a part of the TiDB ent ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v2.0/tools/tidb-binlog-kafka.md b/v2.0/tools/tidb-binlog-kafka.md index f89e7dcb64247..384966d767885 100755 --- a/v2.0/tools/tidb-binlog-kafka.md +++ b/v2.0/tools/tidb-binlog-kafka.md @@ -45,8 +45,8 @@ The Kafka cluster stores the binlog data written by Pump and provides the binlog ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-binlog-latest-linux-amd64.sha256 @@ -370,8 +370,8 @@ CentOS 7+ ```bash # Download PbReader package -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c pb_reader-latest-linux-amd64.sha256 diff --git a/v2.0/tools/tidb-binlog.md b/v2.0/tools/tidb-binlog.md index fe065cc7a518e..fc63f6a1ef8e2 100755 --- a/v2.0/tools/tidb-binlog.md +++ b/v2.0/tools/tidb-binlog.md @@ -37,8 +37,8 @@ Drainer collects binlog files from each Pump node, converts them into specified ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-binlog-latest-linux-amd64.sha256 diff --git a/v2.1-legacy/op-guide/ansible-deployment-rolling-update.md b/v2.1-legacy/op-guide/ansible-deployment-rolling-update.md index 79a734022fd3d..6fac326bb46c2 100755 --- a/v2.1-legacy/op-guide/ansible-deployment-rolling-update.md +++ b/v2.1-legacy/op-guide/ansible-deployment-rolling-update.md @@ -53,7 +53,7 @@ When you perform a rolling update for a TiDB cluster, the service is shut down s You can also download the binary manually. Use `wget` to download the binary and replace the existing binary in `/home/tidb/tidb-ansible/resource/bin/` with it manually. ``` -wget http://download.pingcap.org/tidb-v2.0.7-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-v2.0.7-linux-amd64.tar.gz ``` > **Note:** @@ -63,7 +63,7 @@ wget http://download.pingcap.org/tidb-v2.0.7-linux-amd64.tar.gz If you use `tidb-ansible` of the master branch, download the binary using the following command: ``` -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz ``` ### Perform a rolling update using Ansible diff --git a/v2.1-legacy/op-guide/backup-restore.md b/v2.1-legacy/op-guide/backup-restore.md index c1fa6709446a1..e8a240eb5f2e6 100755 --- a/v2.1-legacy/op-guide/backup-restore.md +++ b/v2.1-legacy/op-guide/backup-restore.md @@ -25,8 +25,8 @@ Use the following tools for data backup and restoration: ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v2.1-legacy/op-guide/migration-overview.md b/v2.1-legacy/op-guide/migration-overview.md index 13ea374384049..bf76ee2d1e38b 100755 --- a/v2.1-legacy/op-guide/migration-overview.md +++ b/v2.1-legacy/op-guide/migration-overview.md @@ -56,8 +56,8 @@ See [Download the TiDB toolset](#download-the-tidb-toolset-linux) to download th ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v2.1-legacy/op-guide/migration.md b/v2.1-legacy/op-guide/migration.md index 868ba8039acce..034c9716d45c8 100755 --- a/v2.1-legacy/op-guide/migration.md +++ b/v2.1-legacy/op-guide/migration.md @@ -109,8 +109,8 @@ See [Download the TiDB enterprise toolset](#download-the-tidb-enterprise-toolset ```bash # Download the enterprise tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v2.1-legacy/scripts/upload.py b/v2.1-legacy/scripts/upload.py index d43a1042c5fb3..6aa6cce99b506 100755 --- a/v2.1-legacy/scripts/upload.py +++ b/v2.1-legacy/scripts/upload.py @@ -36,4 +36,4 @@ def upload(local_file, remote_name, ttl=3600): remote_name = sys.argv[2] upload(local_file, remote_name) - print("http://download.pingcap.org/{}".format(remote_name)) + print("https://download.pingcap.org/{}".format(remote_name)) diff --git a/v2.1-legacy/tikv/deploy-tikv-using-binary.md b/v2.1-legacy/tikv/deploy-tikv-using-binary.md index 7474cfd1a2747..0dda3c20cffd1 100755 --- a/v2.1-legacy/tikv/deploy-tikv-using-binary.md +++ b/v2.1-legacy/tikv/deploy-tikv-using-binary.md @@ -20,7 +20,7 @@ This section describes how to deploy TiKV on a single machine installed with the ```bash # Download the package. wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz - wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 + wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-latest-linux-amd64.sha256 @@ -90,7 +90,7 @@ To deploy a TiKV cluster with multiple nodes for test, take the following steps: ```bash # Download the package. wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz - wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 + wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-latest-linux-amd64.sha256 diff --git a/v2.1-legacy/tispark/tispark-user-guide.md b/v2.1-legacy/tispark/tispark-user-guide.md index 7423e14260884..20853b132f585 100755 --- a/v2.1-legacy/tispark/tispark-user-guide.md +++ b/v2.1-legacy/tispark/tispark-user-guide.md @@ -92,7 +92,7 @@ For the hybrid deployment of TiKV and TiSpark, add TiSpark required resources to ## Deploy the TiSpark cluster -Download TiSpark's jar package [here](http://download.pingcap.org/tispark-0.1.0-SNAPSHOT-jar-with-dependencies.jar). +Download TiSpark's jar package [here](https://download.pingcap.org/tispark-0.1.0-SNAPSHOT-jar-with-dependencies.jar). ### Deploy TiSpark on the existing Spark cluster diff --git a/v2.1-legacy/tools/data-migration-deployment.md b/v2.1-legacy/tools/data-migration-deployment.md index 15c7d4336070e..2ccdbbe3d84fb 100755 --- a/v2.1-legacy/tools/data-migration-deployment.md +++ b/v2.1-legacy/tools/data-migration-deployment.md @@ -108,7 +108,7 @@ Make sure you have logged in to the Control Machine using the `root` user accoun 2. Run the following command to download DM-Ansible. ```bash - $ wget http://download.pingcap.org/dm-ansible.tar.gz + $ wget https://download.pingcap.org/dm-ansible.tar.gz ``` ## Step 4: Install Ansible and its dependencies on the Control Machine @@ -418,7 +418,7 @@ dm_master ansible_host=172.16.10.71 dm_master_port=12080 dm_master_status_port=1 ``` $ cd /home/tidb - $ wget http://download.pingcap.org/dm-ansible.tar.gz + $ wget https://download.pingcap.org/dm-ansible.tar.gz $ tar -xzvf dm-ansible.tar.gz ``` diff --git a/v2.1-legacy/tools/loader.md b/v2.1-legacy/tools/loader.md index df2fa3764cde3..9ca9c6140a14d 100755 --- a/v2.1-legacy/tools/loader.md +++ b/v2.1-legacy/tools/loader.md @@ -10,7 +10,7 @@ category: advanced Loader is a data import tool to load data to TiDB. -[Download the Binary](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz). +[Download the Binary](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz). ## Why did we develop Loader? diff --git a/v2.1-legacy/tools/mydumper.md b/v2.1-legacy/tools/mydumper.md index 4a605c22d327f..254fc7611ae2b 100755 --- a/v2.1-legacy/tools/mydumper.md +++ b/v2.1-legacy/tools/mydumper.md @@ -10,7 +10,7 @@ category: tools `mydumper` is a fork of the [mydumper](https://github.com/maxbube/mydumper) project with additional functionality specific to TiDB. It is the recommended method to use for logical backups of TiDB. -[Download the Binary](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz). +[Download the Binary](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz). ## What enhancements does this contain over regular mydumper? diff --git a/v2.1-legacy/tools/syncer.md b/v2.1-legacy/tools/syncer.md index 82c8b7fc31bbc..063a78796880c 100755 --- a/v2.1-legacy/tools/syncer.md +++ b/v2.1-legacy/tools/syncer.md @@ -18,8 +18,8 @@ Syncer is a tool used to import data incrementally. It is a part of the TiDB ent ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-enterprise-tools-latest-linux-amd64.sha256 diff --git a/v2.1-legacy/tools/tidb-binlog-kafka.md b/v2.1-legacy/tools/tidb-binlog-kafka.md index 3bbf4243e7006..86410bdd9bdf5 100755 --- a/v2.1-legacy/tools/tidb-binlog-kafka.md +++ b/v2.1-legacy/tools/tidb-binlog-kafka.md @@ -53,8 +53,8 @@ The corresponding relationship between the `tidb-ansible` branch and the TiDB ve ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-binlog-kafka-linux-amd64.sha256 @@ -382,8 +382,8 @@ CentOS 7+ ```bash # Download PbReader package -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c pb_reader-latest-linux-amd64.sha256 diff --git a/v2.1-legacy/tools/tidb-binlog.md b/v2.1-legacy/tools/tidb-binlog.md index 8e4011c425bd3..e83907ce1b323 100755 --- a/v2.1-legacy/tools/tidb-binlog.md +++ b/v2.1-legacy/tools/tidb-binlog.md @@ -37,8 +37,8 @@ Drainer collects binlog files from each Pump node, converts them into specified ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-binlog-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-binlog-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-binlog-latest-linux-amd64.sha256 diff --git a/v2.1/how-to/deploy/data-migration-with-ansible.md b/v2.1/how-to/deploy/data-migration-with-ansible.md index 6eaed83ab6cef..df5a87a3ce456 100644 --- a/v2.1/how-to/deploy/data-migration-with-ansible.md +++ b/v2.1/how-to/deploy/data-migration-with-ansible.md @@ -112,7 +112,7 @@ Make sure you have logged in to the Control Machine using the `tidb` user accoun 2. Run the following command to download DM-Ansible. ```bash - $ wget http://download.pingcap.org/dm-ansible-{version}.tar.gz + $ wget https://download.pingcap.org/dm-ansible-{version}.tar.gz ``` `{version}` is the DM version that you expect to download, like `v1.0.1` and `v1.0.2`. @@ -465,7 +465,7 @@ dm_master ansible_host=172.16.10.71 dm_master_port=18261 ``` $ cd /home/tidb - $ wget http://download.pingcap.org/dm-ansible-{version}.tar.gz + $ wget https://download.pingcap.org/dm-ansible-{version}.tar.gz $ tar -xzvf dm-ansible-{version}.tar.gz $ mv dm-ansible-{version} dm-ansible ``` diff --git a/v2.1/how-to/deploy/from-tarball/production-environment.md b/v2.1/how-to/deploy/from-tarball/production-environment.md index 8a25d4b18f4b7..def200446e4b8 100644 --- a/v2.1/how-to/deploy/from-tarball/production-environment.md +++ b/v2.1/how-to/deploy/from-tarball/production-environment.md @@ -106,8 +106,8 @@ See the following table for the default ports for the optional TiDB components: ``` # Download the package. -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-latest-linux-amd64.sha256 diff --git a/v2.1/how-to/deploy/from-tarball/testing-environment.md b/v2.1/how-to/deploy/from-tarball/testing-environment.md index fcba251e30011..e1796e53c6a91 100644 --- a/v2.1/how-to/deploy/from-tarball/testing-environment.md +++ b/v2.1/how-to/deploy/from-tarball/testing-environment.md @@ -106,8 +106,8 @@ See the following table for the default ports for the optional TiDB components: ``` # Download the package. -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-latest-linux-amd64.sha256 diff --git a/v2.1/how-to/get-started/data-migration.md b/v2.1/how-to/get-started/data-migration.md index 9b1706ad4d1c6..66045131f0b90 100644 --- a/v2.1/how-to/get-started/data-migration.md +++ b/v2.1/how-to/get-started/data-migration.md @@ -41,8 +41,8 @@ We're going to deploy 3 instances of MySQL Server, and 1 instance each of pd-ser ```bash sudo yum install -y http://repo.mysql.com/yum/mysql-5.7-community/el/7/x86_64/mysql57-community-release-el7-10.noarch.rpm sudo yum install -y mysql-community-server - curl http://download.pingcap.org/tidb-v2.1-linux-amd64.tar.gz | tar xzf - - curl http://download.pingcap.org/dm-v1.0.2-linux-amd64.tar.gz | tar xzf - + curl https://download.pingcap.org/tidb-v2.1-linux-amd64.tar.gz | tar xzf - + curl https://download.pingcap.org/dm-v1.0.2-linux-amd64.tar.gz | tar xzf - curl -L https://github.com/pingcap/docs/raw/master/dev/how-to/get-started/dm-cnf/dm-cnf.tgz | tar xvzf - ``` diff --git a/v2.1/how-to/get-started/deploy-tidb-from-binary.md b/v2.1/how-to/get-started/deploy-tidb-from-binary.md index 9b34b833bd935..293931a7a021b 100644 --- a/v2.1/how-to/get-started/deploy-tidb-from-binary.md +++ b/v2.1/how-to/get-started/deploy-tidb-from-binary.md @@ -57,8 +57,8 @@ See the [production deployment](/v2.1/how-to/deploy/from-tarball/production-envi ``` # Download the package. -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz -$ wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz +$ wget https://download.pingcap.org/tidb-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-latest-linux-amd64.sha256 diff --git a/v2.1/how-to/get-started/tidb-binlog.md b/v2.1/how-to/get-started/tidb-binlog.md index a0dfb192d30f6..1d33f3b6f51b9 100644 --- a/v2.1/how-to/get-started/tidb-binlog.md +++ b/v2.1/how-to/get-started/tidb-binlog.md @@ -45,14 +45,14 @@ sudo yum install -y mariadb-server Even if you've already started a TiDB cluster, it will be easier to follow along with this tutorial where we will set up a new, simple cluster. We will install from a tarball, using a simplified form of the [Local Deployment](/v2.1/how-to/get-started/deploy-tidb-from-binary.md) guide. You may also wish to refer to [Testing Deployment from Binary Tarball](/v2.1/how-to/deploy/from-tarball/testing-environment.md) for best practices of establishing a real testing deployment, but that goes beyond the scope of this tutorial. ```bash -curl -L http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz | tar xzf - +curl -L https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz | tar xzf - cd tidb-latest-linux-amd64 ``` Expected output: ``` -[kolbe@localhost ~]$ curl -LO http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz | tar xzf - +[kolbe@localhost ~]$ curl -LO https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz | tar xzf - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 368M 100 368M 0 0 8394k 0 0:00:44 0:00:44 --:--:-- 11.1M diff --git a/v2.1/how-to/get-started/tidb-lightning.md b/v2.1/how-to/get-started/tidb-lightning.md index edcc7d36a37ed..4f030430a33a2 100644 --- a/v2.1/how-to/get-started/tidb-lightning.md +++ b/v2.1/how-to/get-started/tidb-lightning.md @@ -57,7 +57,7 @@ Before the data import, you need to deploy a TiDB cluster (later than v2.0.9). I Download the TiDB Lightning installation package from the following link: -- **v3.0.4**: [tidb-toolkit-v3.0.4-linux-amd64.tar.gz](http://download.pingcap.org/tidb-toolkit-v3.0.0-linux-amd64.tar.gz) +- **v3.0.4**: [tidb-toolkit-v3.0.4-linux-amd64.tar.gz](https://download.pingcap.org/tidb-toolkit-v3.0.0-linux-amd64.tar.gz) > **Note:** > diff --git a/v2.1/how-to/maintain/backup-and-restore.md b/v2.1/how-to/maintain/backup-and-restore.md index 3e82c02e9d394..179aebc9cb228 100644 --- a/v2.1/how-to/maintain/backup-and-restore.md +++ b/v2.1/how-to/maintain/backup-and-restore.md @@ -26,8 +26,8 @@ Use the following tools for data backup and restoration: {{< copyable "shell-regular" >}} ```bash - wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz && \ - wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 + wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz && \ + wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 ``` 2. Check the file integrity. If the result is fine, the file is correct. diff --git a/v2.1/reference/tidb-binlog/reparo.md b/v2.1/reference/tidb-binlog/reparo.md index d99e91a35085d..8809715c20393 100644 --- a/v2.1/reference/tidb-binlog/reparo.md +++ b/v2.1/reference/tidb-binlog/reparo.md @@ -8,7 +8,7 @@ category: reference Reparo is a TiDB Binlog tool, used to recover the incremental data. To back up the incremental data, you can use Drainer of TiDB Binlog to output the binlog data in the protobuf format to files. To restore the incremental data, you can use Reparo to parse the binlog data in the files and apply the binlog in TiDB/MySQL. -Download Reparo via [tidb-binlog-cluster-latest-linux-amd64.tar.gz](http://download.pingcap.org/tidb-binlog-cluster-latest-linux-amd64.tar.gz) +Download Reparo via [tidb-binlog-cluster-latest-linux-amd64.tar.gz](https://download.pingcap.org/tidb-binlog-cluster-latest-linux-amd64.tar.gz) ## Reparo usage diff --git a/v2.1/reference/tidb-binlog/tidb-binlog-kafka.md b/v2.1/reference/tidb-binlog/tidb-binlog-kafka.md index cdadcb845c75b..e12520cd61ceb 100644 --- a/v2.1/reference/tidb-binlog/tidb-binlog-kafka.md +++ b/v2.1/reference/tidb-binlog/tidb-binlog-kafka.md @@ -53,8 +53,8 @@ The corresponding relationship between the `tidb-ansible` branch and the TiDB ve ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-binlog-kafka-linux-amd64.sha256 @@ -382,8 +382,8 @@ CentOS 7+ ```bash # Download PbReader package -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c pb_reader-latest-linux-amd64.sha256 diff --git a/v2.1/reference/tispark.md b/v2.1/reference/tispark.md index 4c6946ac7aebb..57f80614a2609 100644 --- a/v2.1/reference/tispark.md +++ b/v2.1/reference/tispark.md @@ -76,7 +76,7 @@ For the hybrid deployment of TiKV and TiSpark, add TiSpark required resources to ## Deploy the TiSpark cluster -Download TiSpark's jar package [here](http://download.pingcap.org/tispark-latest-linux-amd64.tar.gz), decompress it, and copy the content to the appropriate folder. +Download TiSpark's jar package [here](https://download.pingcap.org/tispark-latest-linux-amd64.tar.gz), decompress it, and copy the content to the appropriate folder. ### Deploy TiSpark on the existing Spark cluster diff --git a/v2.1/reference/tools/download.md b/v2.1/reference/tools/download.md index 310830f9ccb28..37acde789b424 100644 --- a/v2.1/reference/tools/download.md +++ b/v2.1/reference/tools/download.md @@ -16,12 +16,12 @@ In addition, the Kafka version of TiDB Binlog is also provided. | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (TiDB Binlog) | Linux | amd64 | `http://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | -| `http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz` (the Kafka version of TiDB Binlog) | Linux | amd64 | `http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (TiDB Binlog) | Linux | amd64 | `https://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz` (the Kafka version of TiDB Binlog) | Linux | amd64 | `https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v2.1.15` is `http://download.pingcap.org/tidb-v2.1.15-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v2.1.15` is `https://download.pingcap.org/tidb-v2.1.15-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## TiDB Lightning @@ -29,11 +29,11 @@ Download [TiDB Lightning](/v2.1/reference/tools/tidb-lightning/overview.md) by u | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.tar.gz` | Linux | amd64 | `http://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.tar.gz` | Linux | amd64 | `https://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v2.1.15` is `http://download.pingcap.org/tidb-toolkit-v2.1.15-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v2.1.15` is `https://download.pingcap.org/tidb-toolkit-v2.1.15-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## TiDB DM (Data Migration) @@ -41,11 +41,11 @@ Download [DM](/v2.1/reference/tools/data-migration/overview.md) by using the dow | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/dm-{version}-linux-amd64.tar.gz` | Linux | amd64 | `http://download.pingcap.org/dm-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/dm-{version}-linux-amd64.tar.gz` | Linux | amd64 | `https://download.pingcap.org/dm-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v1.0.1` is `http://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v1.0.1` is `https://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## Syncer, Loader, and Mydumper @@ -53,7 +53,7 @@ If you want to download the latest version of [Syncer](/v2.1/reference/tools/syn | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| [tidb-enterprise-tools-latest-linux-amd64.tar.gz](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz) | Linux | amd64 | [tidb-enterprise-tools-latest-linux-amd64.sha256](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256) | +| [tidb-enterprise-tools-latest-linux-amd64.tar.gz](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz) | Linux | amd64 | [tidb-enterprise-tools-latest-linux-amd64.sha256](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256) | This enterprise tools package includes all the following tools: diff --git a/v2.1/reference/tools/pd-control.md b/v2.1/reference/tools/pd-control.md index c772d23437015..9ba43948b2187 100644 --- a/v2.1/reference/tools/pd-control.md +++ b/v2.1/reference/tools/pd-control.md @@ -23,11 +23,11 @@ If you want to download the latest version of `pd-ctl`, directly download the Ti | Package download link | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `http://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `https://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v2.1.18`, the package download link is `http://download.pingcap.org/tidb-v2.1.18-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v2.1.18`, the package download link is `https://download.pingcap.org/tidb-v2.1.18-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## Usage diff --git a/v2.1/tispark/tispark-user-guide_v1.x.md b/v2.1/tispark/tispark-user-guide_v1.x.md index 0d64e23db3dd8..81f23f7c365d2 100644 --- a/v2.1/tispark/tispark-user-guide_v1.x.md +++ b/v2.1/tispark/tispark-user-guide_v1.x.md @@ -92,7 +92,7 @@ For the hybrid deployment of TiKV and TiSpark, add TiSpark required resources to ## Deploy the TiSpark cluster -Download TiSpark's jar package [here](http://download.pingcap.org/tispark-0.1.0-SNAPSHOT-jar-with-dependencies.jar). +Download TiSpark's jar package [here](https://download.pingcap.org/tispark-0.1.0-SNAPSHOT-jar-with-dependencies.jar). ### Deploy TiSpark on the existing Spark cluster diff --git a/v3.0/how-to/deploy/data-migration-with-ansible.md b/v3.0/how-to/deploy/data-migration-with-ansible.md index 10cb59b7cea0c..595b659007bd3 100644 --- a/v3.0/how-to/deploy/data-migration-with-ansible.md +++ b/v3.0/how-to/deploy/data-migration-with-ansible.md @@ -113,7 +113,7 @@ Make sure you have logged in to the Control Machine using the `tidb` user accoun 2. Run the following command to download DM-Ansible. ```bash - $ wget http://download.pingcap.org/dm-ansible-{version}.tar.gz + $ wget https://download.pingcap.org/dm-ansible-{version}.tar.gz ``` `{version}` is the DM version that you expect to download, like `v1.0.1` and `v1.0.2`. @@ -466,7 +466,7 @@ dm_master ansible_host=172.16.10.71 dm_master_port=18261 ``` $ cd /home/tidb - $ wget http://download.pingcap.org/dm-ansible-{version}.tar.gz + $ wget https://download.pingcap.org/dm-ansible-{version}.tar.gz $ tar -xzvf dm-ansible-{version}.tar.gz $ mv dm-ansible-{version} dm-ansible ``` diff --git a/v3.0/how-to/deploy/from-tarball/production-environment.md b/v3.0/how-to/deploy/from-tarball/production-environment.md index bf9ea93a7f922..97f111f303b09 100644 --- a/v3.0/how-to/deploy/from-tarball/production-environment.md +++ b/v3.0/how-to/deploy/from-tarball/production-environment.md @@ -107,7 +107,7 @@ See the following table for the default ports for the optional TiDB components: ``` # Download the package. -$ wget http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz http://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz https://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-v3.0-linux-amd64.sha256 diff --git a/v3.0/how-to/deploy/from-tarball/testing-environment.md b/v3.0/how-to/deploy/from-tarball/testing-environment.md index 9ad484fecfe73..4b99443548c7c 100644 --- a/v3.0/how-to/deploy/from-tarball/testing-environment.md +++ b/v3.0/how-to/deploy/from-tarball/testing-environment.md @@ -107,7 +107,7 @@ See the following table for the default ports for the optional TiDB components: ``` # Download the package. -$ wget http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz http://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz https://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-v3.0-linux-amd64.sha256 diff --git a/v3.0/how-to/get-started/data-migration.md b/v3.0/how-to/get-started/data-migration.md index 13b09e151497c..54620a7b3b56b 100644 --- a/v3.0/how-to/get-started/data-migration.md +++ b/v3.0/how-to/get-started/data-migration.md @@ -41,8 +41,8 @@ We're going to deploy 3 instances of MySQL Server, and 1 instance each of pd-ser ```bash sudo yum install -y http://repo.mysql.com/yum/mysql-5.7-community/el/7/x86_64/mysql57-community-release-el7-10.noarch.rpm sudo yum install -y mysql-community-server - curl http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - - curl http://download.pingcap.org/dm-v1.0.2-linux-amd64.tar.gz | tar xzf - + curl https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - + curl https://download.pingcap.org/dm-v1.0.2-linux-amd64.tar.gz | tar xzf - curl -L https://github.com/pingcap/docs/raw/master/dev/how-to/get-started/dm-cnf/dm-cnf.tgz | tar xvzf - ``` diff --git a/v3.0/how-to/get-started/deploy-tidb-from-binary.md b/v3.0/how-to/get-started/deploy-tidb-from-binary.md index b16b129e13314..e8e3287ce105a 100644 --- a/v3.0/how-to/get-started/deploy-tidb-from-binary.md +++ b/v3.0/how-to/get-started/deploy-tidb-from-binary.md @@ -57,7 +57,7 @@ See the [production deployment](/v3.0/how-to/deploy/from-tarball/production-envi ``` # Download the package. -$ wget http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz http://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz https://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-v3.0-linux-amd64.sha256 diff --git a/v3.0/how-to/get-started/tidb-binlog.md b/v3.0/how-to/get-started/tidb-binlog.md index e9d226a801e47..b01eaf3746517 100644 --- a/v3.0/how-to/get-started/tidb-binlog.md +++ b/v3.0/how-to/get-started/tidb-binlog.md @@ -45,14 +45,14 @@ sudo yum install -y mariadb-server Even if you've already started a TiDB cluster, it will be easier to follow along with this tutorial where we will set up a new, simple cluster. We will install from a tarball, using a simplified form of the [Local Deployment](/v3.0/how-to/get-started/deploy-tidb-from-binary.md) guide. You may also wish to refer to [Testing Deployment from Binary Tarball](/v3.0/how-to/deploy/from-tarball/testing-environment.md) for best practices of establishing a real testing deployment, but that goes beyond the scope of this tutorial. ```bash -curl -L http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - +curl -L https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - cd tidb-v3.0-linux-amd64/ ``` Expected output: ``` -[kolbe@localhost ~]$ curl -LO http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - +[kolbe@localhost ~]$ curl -LO https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 279M 100 279M 0 0 4983k 0 0:00:57 0:00:57 --:--:-- 3638k diff --git a/v3.0/how-to/get-started/tidb-lightning.md b/v3.0/how-to/get-started/tidb-lightning.md index d4ada76084f65..2cbe1990a4c3f 100644 --- a/v3.0/how-to/get-started/tidb-lightning.md +++ b/v3.0/how-to/get-started/tidb-lightning.md @@ -57,7 +57,7 @@ Before the data import, you need to deploy a TiDB cluster (later than v2.0.9). I Download the TiDB Lightning installation package from the following link: -- **v3.0.4**: [tidb-toolkit-v3.0.4-linux-amd64.tar.gz](http://download.pingcap.org/tidb-toolkit-v3.0.0-linux-amd64.tar.gz) +- **v3.0.4**: [tidb-toolkit-v3.0.4-linux-amd64.tar.gz](https://download.pingcap.org/tidb-toolkit-v3.0.0-linux-amd64.tar.gz) > **Note:** > diff --git a/v3.0/how-to/maintain/backup-and-restore.md b/v3.0/how-to/maintain/backup-and-restore.md index 77670d1b787d0..68a8b6681479d 100644 --- a/v3.0/how-to/maintain/backup-and-restore.md +++ b/v3.0/how-to/maintain/backup-and-restore.md @@ -27,8 +27,8 @@ Use the following tools for data backup and restoration: {{< copyable "shell-regular" >}} ```bash - wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz && \ - wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 + wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz && \ + wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 ``` 2. Check the file integrity. If the result is fine, the file is correct. diff --git a/v3.0/reference/tidb-binlog/reparo.md b/v3.0/reference/tidb-binlog/reparo.md index 98c913d698fa5..7ddec2f6f71a7 100644 --- a/v3.0/reference/tidb-binlog/reparo.md +++ b/v3.0/reference/tidb-binlog/reparo.md @@ -9,7 +9,7 @@ aliases: ['/docs/tools/binlog/reparo/'] Reparo is a TiDB Binlog tool, used to recover the incremental data. To back up the incremental data, you can use Drainer of TiDB Binlog to output the binlog data in the protobuf format to files. To restore the incremental data, you can use Reparo to parse the binlog data in the files and apply the binlog in TiDB/MySQL. -Download Reparo via [tidb-binlog-cluster-latest-linux-amd64.tar.gz](http://download.pingcap.org/tidb-binlog-cluster-latest-linux-amd64.tar.gz) +Download Reparo via [tidb-binlog-cluster-latest-linux-amd64.tar.gz](https://download.pingcap.org/tidb-binlog-cluster-latest-linux-amd64.tar.gz) ## Reparo usage diff --git a/v3.0/reference/tidb-binlog/tidb-binlog-kafka.md b/v3.0/reference/tidb-binlog/tidb-binlog-kafka.md index 85d773e93b4d8..069ee33977f8c 100644 --- a/v3.0/reference/tidb-binlog/tidb-binlog-kafka.md +++ b/v3.0/reference/tidb-binlog/tidb-binlog-kafka.md @@ -54,8 +54,8 @@ The corresponding relationship between the `tidb-ansible` branch and the TiDB ve ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-binlog-kafka-linux-amd64.sha256 @@ -383,8 +383,8 @@ CentOS 7+ ```bash # Download PbReader package -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c pb_reader-latest-linux-amd64.sha256 diff --git a/v3.0/reference/tools/download.md b/v3.0/reference/tools/download.md index d3594f316588f..9a7d7e8ee5258 100644 --- a/v3.0/reference/tools/download.md +++ b/v3.0/reference/tools/download.md @@ -17,12 +17,12 @@ In addition, the Kafka version of TiDB Binlog is also provided. | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (TiDB Binlog) | Linux | amd64 | `http://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | -| `http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz` (the Kafka version of TiDB Binlog) | Linux | amd64 | `http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (TiDB Binlog) | Linux | amd64 | `https://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz` (the Kafka version of TiDB Binlog) | Linux | amd64 | `https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v3.0.5` is `http://download.pingcap.org/tidb-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v3.0.5` is `https://download.pingcap.org/tidb-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## TiDB Lightning @@ -30,11 +30,11 @@ Download [TiDB Lightning](/v3.0/reference/tools/tidb-lightning/overview.md) by u | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.tar.gz` | Linux | amd64 | `http://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.tar.gz` | Linux | amd64 | `https://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v3.0.5` is `http://download.pingcap.org/tidb-toolkit-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v3.0.5` is `https://download.pingcap.org/tidb-toolkit-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## TiDB DM (Data Migration) @@ -42,11 +42,11 @@ Download [DM](/v3.0/reference/tools/data-migration/overview.md) by using the dow | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/dm-{version}-linux-amd64.tar.gz` | Linux | amd64 | `http://download.pingcap.org/dm-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/dm-{version}-linux-amd64.tar.gz` | Linux | amd64 | `https://download.pingcap.org/dm-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v1.0.1` is `http://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v1.0.1` is `https://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## Syncer, Loader, and Mydumper @@ -54,7 +54,7 @@ If you want to download the latest version of [Syncer](/v3.0/reference/tools/syn | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| [tidb-enterprise-tools-latest-linux-amd64.tar.gz](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz) | Linux | amd64 | [tidb-enterprise-tools-latest-linux-amd64.sha256](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256) | +| [tidb-enterprise-tools-latest-linux-amd64.tar.gz](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz) | Linux | amd64 | [tidb-enterprise-tools-latest-linux-amd64.sha256](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256) | This enterprise tools package includes all the following tools: diff --git a/v3.0/reference/tools/pd-control.md b/v3.0/reference/tools/pd-control.md index 612ba1a94dfec..09f7ba95958e0 100644 --- a/v3.0/reference/tools/pd-control.md +++ b/v3.0/reference/tools/pd-control.md @@ -24,11 +24,11 @@ If you want to download the latest version of `pd-ctl`, directly download the Ti | Package download link | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `http://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `https://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v3.0.7`, the package download link is `http://download.pingcap.org/tidb-v3.0.7-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v3.0.7`, the package download link is `https://download.pingcap.org/tidb-v3.0.7-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## Usage diff --git a/v3.1/how-to/deploy/data-migration-with-ansible.md b/v3.1/how-to/deploy/data-migration-with-ansible.md index 05031406431ed..cd5a67fdae8b7 100644 --- a/v3.1/how-to/deploy/data-migration-with-ansible.md +++ b/v3.1/how-to/deploy/data-migration-with-ansible.md @@ -112,7 +112,7 @@ Make sure you have logged in to the Control Machine using the `tidb` user accoun 2. Run the following command to download DM-Ansible. ```bash - $ wget http://download.pingcap.org/dm-ansible-{version}.tar.gz + $ wget https://download.pingcap.org/dm-ansible-{version}.tar.gz ``` `{version}` is the DM version that you expect to download, like `v1.0.1` and `v1.0.2`. @@ -465,7 +465,7 @@ dm_master ansible_host=172.16.10.71 dm_master_port=18261 ``` $ cd /home/tidb - $ wget http://download.pingcap.org/dm-ansible-{version}.tar.gz + $ wget https://download.pingcap.org/dm-ansible-{version}.tar.gz $ tar -xzvf dm-ansible-{version}.tar.gz $ mv dm-ansible-{version} dm-ansible ``` diff --git a/v3.1/how-to/deploy/from-tarball/production-environment.md b/v3.1/how-to/deploy/from-tarball/production-environment.md index 2e028816303a9..615a9e5bb102d 100644 --- a/v3.1/how-to/deploy/from-tarball/production-environment.md +++ b/v3.1/how-to/deploy/from-tarball/production-environment.md @@ -106,7 +106,7 @@ See the following table for the default ports for the optional TiDB components: ``` # Download the package. -$ wget http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz http://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz https://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-v3.0-linux-amd64.sha256 diff --git a/v3.1/how-to/deploy/from-tarball/testing-environment.md b/v3.1/how-to/deploy/from-tarball/testing-environment.md index 0a38f77e5d50c..13013ca28413d 100644 --- a/v3.1/how-to/deploy/from-tarball/testing-environment.md +++ b/v3.1/how-to/deploy/from-tarball/testing-environment.md @@ -106,7 +106,7 @@ See the following table for the default ports for the optional TiDB components: ``` # Download the package. -$ wget http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz http://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz https://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-v3.0-linux-amd64.sha256 diff --git a/v3.1/how-to/get-started/data-migration.md b/v3.1/how-to/get-started/data-migration.md index 48f3c89194313..ad719efa7df47 100644 --- a/v3.1/how-to/get-started/data-migration.md +++ b/v3.1/how-to/get-started/data-migration.md @@ -41,8 +41,8 @@ We're going to deploy 3 instances of MySQL Server, and 1 instance each of pd-ser ```bash sudo yum install -y http://repo.mysql.com/yum/mysql-5.7-community/el/7/x86_64/mysql57-community-release-el7-10.noarch.rpm sudo yum install -y mysql-community-server - curl http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - - curl http://download.pingcap.org/dm-v1.0.2-linux-amd64.tar.gz | tar xzf - + curl https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - + curl https://download.pingcap.org/dm-v1.0.2-linux-amd64.tar.gz | tar xzf - curl -L https://github.com/pingcap/docs/raw/master/dev/how-to/get-started/dm-cnf/dm-cnf.tgz | tar xvzf - ``` diff --git a/v3.1/how-to/get-started/deploy-tidb-from-binary.md b/v3.1/how-to/get-started/deploy-tidb-from-binary.md index 304f3c533c579..ed3bc238209d6 100644 --- a/v3.1/how-to/get-started/deploy-tidb-from-binary.md +++ b/v3.1/how-to/get-started/deploy-tidb-from-binary.md @@ -56,7 +56,7 @@ See the [production deployment](/v3.1/how-to/deploy/from-tarball/production-envi ``` # Download the package. -$ wget http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz http://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 +$ wget https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz https://download.pingcap.org/tidb-v3.0-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. $ sha256sum -c tidb-v3.0-linux-amd64.sha256 diff --git a/v3.1/how-to/get-started/tidb-binlog.md b/v3.1/how-to/get-started/tidb-binlog.md index 7eb1c520a1073..87ae8cddd0c81 100644 --- a/v3.1/how-to/get-started/tidb-binlog.md +++ b/v3.1/how-to/get-started/tidb-binlog.md @@ -45,14 +45,14 @@ sudo yum install -y mariadb-server Even if you've already started a TiDB cluster, it will be easier to follow along with this tutorial where we will set up a new, simple cluster. We will install from a tarball, using a simplified form of the [Local Deployment](/v3.1/how-to/get-started/deploy-tidb-from-binary.md) guide. You may also wish to refer to [Testing Deployment from Binary Tarball](/v3.1/how-to/deploy/from-tarball/testing-environment.md) for best practices of establishing a real testing deployment, but that goes beyond the scope of this tutorial. ```bash -curl -L http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - +curl -L https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - cd tidb-v3.0-linux-amd64/ ``` Expected output: ``` -[kolbe@localhost ~]$ curl -LO http://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - +[kolbe@localhost ~]$ curl -LO https://download.pingcap.org/tidb-v3.0-linux-amd64.tar.gz | tar xzf - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 279M 100 279M 0 0 4983k 0 0:00:57 0:00:57 --:--:-- 3638k diff --git a/v3.1/how-to/get-started/tidb-lightning.md b/v3.1/how-to/get-started/tidb-lightning.md index b0d6cf8ad2c61..3d5f1e0dc3061 100644 --- a/v3.1/how-to/get-started/tidb-lightning.md +++ b/v3.1/how-to/get-started/tidb-lightning.md @@ -57,7 +57,7 @@ Before the data import, you need to deploy a TiDB cluster (later than v2.0.9). I Download the TiDB Lightning installation package from the following link: -- **v3.0.4**: [tidb-toolkit-v3.0.4-linux-amd64.tar.gz](http://download.pingcap.org/tidb-toolkit-v3.0.0-linux-amd64.tar.gz) +- **v3.0.4**: [tidb-toolkit-v3.0.4-linux-amd64.tar.gz](https://download.pingcap.org/tidb-toolkit-v3.0.0-linux-amd64.tar.gz) > **Note:** > diff --git a/v3.1/how-to/maintain/backup-and-restore/mydumper-loader.md b/v3.1/how-to/maintain/backup-and-restore/mydumper-loader.md index eddff6d1cec7d..84056cf2406d1 100644 --- a/v3.1/how-to/maintain/backup-and-restore/mydumper-loader.md +++ b/v3.1/how-to/maintain/backup-and-restore/mydumper-loader.md @@ -27,8 +27,8 @@ Use the following tools for data backup and restoration: {{< copyable "shell-regular" >}} ```bash - wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz && \ - wget http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 + wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz && \ + wget https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256 ``` 2. Check the file integrity. If the result is fine, the file is correct. diff --git a/v3.1/reference/tidb-binlog/reparo.md b/v3.1/reference/tidb-binlog/reparo.md index d99e91a35085d..8809715c20393 100644 --- a/v3.1/reference/tidb-binlog/reparo.md +++ b/v3.1/reference/tidb-binlog/reparo.md @@ -8,7 +8,7 @@ category: reference Reparo is a TiDB Binlog tool, used to recover the incremental data. To back up the incremental data, you can use Drainer of TiDB Binlog to output the binlog data in the protobuf format to files. To restore the incremental data, you can use Reparo to parse the binlog data in the files and apply the binlog in TiDB/MySQL. -Download Reparo via [tidb-binlog-cluster-latest-linux-amd64.tar.gz](http://download.pingcap.org/tidb-binlog-cluster-latest-linux-amd64.tar.gz) +Download Reparo via [tidb-binlog-cluster-latest-linux-amd64.tar.gz](https://download.pingcap.org/tidb-binlog-cluster-latest-linux-amd64.tar.gz) ## Reparo usage diff --git a/v3.1/reference/tidb-binlog/tidb-binlog-kafka.md b/v3.1/reference/tidb-binlog/tidb-binlog-kafka.md index cdadcb845c75b..e12520cd61ceb 100644 --- a/v3.1/reference/tidb-binlog/tidb-binlog-kafka.md +++ b/v3.1/reference/tidb-binlog/tidb-binlog-kafka.md @@ -53,8 +53,8 @@ The corresponding relationship between the `tidb-ansible` branch and the TiDB ve ```bash # Download the tool package. -wget http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz -wget http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256 +wget https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz +wget https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c tidb-binlog-kafka-linux-amd64.sha256 @@ -382,8 +382,8 @@ CentOS 7+ ```bash # Download PbReader package -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz -wget http://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.tar.gz +wget https://download.pingcap.org/pb_reader-latest-linux-amd64.sha256 # Check the file integrity. If the result is OK, the file is correct. sha256sum -c pb_reader-latest-linux-amd64.sha256 diff --git a/v3.1/reference/tools/download.md b/v3.1/reference/tools/download.md index 40773f01a1303..567617c811a77 100644 --- a/v3.1/reference/tools/download.md +++ b/v3.1/reference/tools/download.md @@ -16,12 +16,12 @@ In addition, the Kafka version of TiDB Binlog is also provided. | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (TiDB Binlog) | Linux | amd64 | `http://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | -| `http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz` (the Kafka version of TiDB Binlog) | Linux | amd64 | `http://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (TiDB Binlog) | Linux | amd64 | `https://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.tar.gz` (the Kafka version of TiDB Binlog) | Linux | amd64 | `https://download.pingcap.org/tidb-binlog-kafka-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v3.0.5` is `http://download.pingcap.org/tidb-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v3.0.5` is `https://download.pingcap.org/tidb-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## TiDB Lightning @@ -29,11 +29,11 @@ Download [TiDB Lightning](/v3.1/reference/tools/tidb-lightning/overview.md) by u | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.tar.gz` | Linux | amd64 | `http://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.tar.gz` | Linux | amd64 | `https://download.pingcap.org/tidb-toolkit-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v3.0.5` is `http://download.pingcap.org/tidb-toolkit-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v3.0.5` is `https://download.pingcap.org/tidb-toolkit-v3.0.5-linux-amd64.tar.gz`. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## TiDB DM (Data Migration) @@ -41,11 +41,11 @@ Download [DM](/v3.1/reference/tools/data-migration/overview.md) by using the dow | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/dm-{version}-linux-amd64.tar.gz` | Linux | amd64 | `http://download.pingcap.org/dm-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/dm-{version}-linux-amd64.tar.gz` | Linux | amd64 | `https://download.pingcap.org/dm-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v1.0.1` is `http://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page. You can also download the latest unpublished version by replacing `{version}` with `latest`. +> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v1.0.1` is `https://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page. You can also download the latest unpublished version by replacing `{version}` with `latest`. ## Syncer, Loader, and Mydumper @@ -53,7 +53,7 @@ If you want to download the latest version of [Syncer](/v3.1/reference/tools/syn | Package name | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| [tidb-enterprise-tools-latest-linux-amd64.tar.gz](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz) | Linux | amd64 | [tidb-enterprise-tools-latest-linux-amd64.sha256](http://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256) | +| [tidb-enterprise-tools-latest-linux-amd64.tar.gz](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.tar.gz) | Linux | amd64 | [tidb-enterprise-tools-latest-linux-amd64.sha256](https://download.pingcap.org/tidb-enterprise-tools-latest-linux-amd64.sha256) | This enterprise tools package includes all the following tools: diff --git a/v3.1/reference/tools/pd-control.md b/v3.1/reference/tools/pd-control.md index ca34d4e26bf27..a2ba69ad7b53d 100644 --- a/v3.1/reference/tools/pd-control.md +++ b/v3.1/reference/tools/pd-control.md @@ -23,11 +23,11 @@ If you want to download the latest version of `pd-ctl`, directly download the Ti | Package download link | OS | Architecture | SHA256 checksum | |:---|:---|:---|:---| -| `http://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `http://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | +| `https://download.pingcap.org/tidb-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `https://download.pingcap.org/tidb-{version}-linux-amd64.sha256` | > **Note:** > -> `{version}` indicates the version number of TiDB. For example, if `{version}` is `latest`, the package download link is `http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz`. The `latest` version is the latest unpublished version. +> `{version}` indicates the version number of TiDB. For example, if `{version}` is `latest`, the package download link is `https://download.pingcap.org/tidb-latest-linux-amd64.tar.gz`. The `latest` version is the latest unpublished version. ## Usage