You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ur...@apache.org on 2022/04/02 01:52:55 UTC
[pulsar-site] branch main updated: fix: some docs fix in 2.1.0 and build scripts optimize
This is an automated email from the ASF dual-hosted git repository.
urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 65aa5e0 fix: some docs fix in 2.1.0 and build scripts optimize
65aa5e0 is described below
commit 65aa5e0931a6cd890b01a545ff9c51e84c4f606c
Author: Li Li <ur...@apache.org>
AuthorDate: Sat Apr 2 09:52:40 2022 +0800
fix: some docs fix in 2.1.0 and build scripts optimize
Signed-off-by: Li Li <ur...@apache.org>
---
.github/workflows/ci-pulsar-website-docs-sync.yaml | 2 +-
site2/website-next/scripts/split-version-build.sh | 4 ++--
.../version-2.1.0-incubating/cookbooks-deduplication.md | 4 ++--
.../versioned_docs/version-2.1.0-incubating/deploy-kubernetes.md | 4 ++--
.../version-2.1.0-incubating/cookbooks-deduplication.md | 4 ++--
.../versioned_docs/version-2.1.0-incubating/deploy-kubernetes.md | 4 ++--
6 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/.github/workflows/ci-pulsar-website-docs-sync.yaml b/.github/workflows/ci-pulsar-website-docs-sync.yaml
index c3bc8f3..83df47d 100644
--- a/.github/workflows/ci-pulsar-website-docs-sync.yaml
+++ b/.github/workflows/ci-pulsar-website-docs-sync.yaml
@@ -53,7 +53,7 @@ jobs:
PULSAR_COMMIT_ID=$(git rev-parse --short HEAD)
- cd ../pulsar-site
+ cd $DIR/pulsar-site
git add -A .
git status
diff --git a/site2/website-next/scripts/split-version-build.sh b/site2/website-next/scripts/split-version-build.sh
index 768d5fe..dbe1ea1 100755
--- a/site2/website-next/scripts/split-version-build.sh
+++ b/site2/website-next/scripts/split-version-build.sh
@@ -21,7 +21,7 @@ function _build() {
}
function _buildVersion() {
- echo "..." $buildVersion " begin build..."
+ echo "..." $buildVersion "begin build..."
if [[ $buildVersion = "next" ]]; then
echo "[\"current\"]" >.build-versions.json
else
@@ -51,7 +51,7 @@ function _buildVersion() {
# Build next version that has any changed
while read version; do
buildVersion=$version
- if [[ $@ == *website-next/versioned_docs/version-$version* || $buildVersion == "next" || $BUILD_ALL_VERSION == "1" || $buildVersion == $BUILD_VERSION ]]; then
+ if [[ $@ == *website-next/versioned_docs/version-$version* || $buildVersion == "next" || $BUILD_ALL_VERSION == "1" || $BUILD_VERSION == *$buildVersion* ]]; then
_buildVersion
else
echo "..." $buildVersion "no change, skip"
diff --git a/site2/website-next/versioned_docs/version-2.1.0-incubating/cookbooks-deduplication.md b/site2/website-next/versioned_docs/version-2.1.0-incubating/cookbooks-deduplication.md
index 0dec67d..eb2327d 100644
--- a/site2/website-next/versioned_docs/version-2.1.0-incubating/cookbooks-deduplication.md
+++ b/site2/website-next/versioned_docs/version-2.1.0-incubating/cookbooks-deduplication.md
@@ -38,7 +38,7 @@ Regardless of the value of `brokerDeduplicationEnabled`, [enabling](#enabling) a
### Enabling message deduplication {#enabling}
-You can enable message deduplication on specific namespaces, regardless of the the [default](#default) for the broker, using the [`pulsar-admin namespace set-deduplication`](reference-pulsar-admin.md#namespace-set-deduplication) command. You can use the `--enable`/`-e` flag and specify the namespace. Here's an example with <tenant>/<namespace>:
+You can enable message deduplication on specific namespaces, regardless of the the [default](#default) for the broker, using the [`pulsar-admin namespace set-deduplication`](reference-pulsar-admin.md#namespace-set-deduplication) command. You can use the `--enable`/`-e` flag and specify the namespace. Here's an example with `<tenant>/<namespace>`:
```bash
@@ -50,7 +50,7 @@ $ bin/pulsar-admin namespaces set-deduplication \
### Disabling message deduplication {#disabling}
-You can disable message deduplication on a specific namespace using the same method shown [above](#enabling), except using the `--disable`/`-d` flag instead. Here's an example with <tenant>/<namespace>:
+You can disable message deduplication on a specific namespace using the same method shown [above](#enabling), except using the `--disable`/`-d` flag instead. Here's an example with `<tenant>/<namespace>`:
```bash
diff --git a/site2/website-next/versioned_docs/version-2.1.0-incubating/deploy-kubernetes.md b/site2/website-next/versioned_docs/version-2.1.0-incubating/deploy-kubernetes.md
index 4ef8a81..73ef125 100644
--- a/site2/website-next/versioned_docs/version-2.1.0-incubating/deploy-kubernetes.md
+++ b/site2/website-next/versioned_docs/version-2.1.0-incubating/deploy-kubernetes.md
@@ -19,7 +19,7 @@ The deployment method shown in this guide relies on [YAML](http://yaml.org/) def
* A two-bookie BookKeeper cluster
* A three-node ZooKeeper cluster
* A three-broker Pulsar cluster
-* A [monitoring stack]() consisting of [Prometheus](https://prometheus.io/), [Grafana](https://grafana.com), and the [Pulsar dashboard](administration-dashboard)
+* A [monitoring stack](#) consisting of [Prometheus](https://prometheus.io/), [Grafana](https://grafana.com), and the [Pulsar dashboard](administration-dashboard)
* A [pod](https://kubernetes.io/docs/concepts/workloads/pods/pod/) from which you can run administrative commands using the [`pulsar-admin`](reference-pulsar-admin) CLI tool
## Setup
@@ -40,7 +40,7 @@ To get started, you'll need:
* A Google Cloud Platform account, which you can sign up for at [cloud.google.com](https://cloud.google.com)
* An existing Cloud Platform project
-* The [Google Cloud SDK](https://cloud.google.com/sdk/downloads) (in particular the [`gcloud`](https://cloud.google.com/sdk/gcloud/) and [`kubectl`]() tools).
+* The [Google Cloud SDK](https://cloud.google.com/sdk/downloads) (in particular the [`gcloud`](https://cloud.google.com/sdk/gcloud/) and [`kubectl`](https://kubernetes.io/docs/reference/kubectl/) tools).
### Create a new Kubernetes cluster
diff --git a/site2/website/versioned_docs/version-2.1.0-incubating/cookbooks-deduplication.md b/site2/website/versioned_docs/version-2.1.0-incubating/cookbooks-deduplication.md
index 6aa401e..021f060 100644
--- a/site2/website/versioned_docs/version-2.1.0-incubating/cookbooks-deduplication.md
+++ b/site2/website/versioned_docs/version-2.1.0-incubating/cookbooks-deduplication.md
@@ -38,7 +38,7 @@ Regardless of the value of `brokerDeduplicationEnabled`, [enabling](#enabling) a
### Enabling message deduplication {#enabling}
-You can enable message deduplication on specific namespaces, regardless of the the [default](#default) for the broker, using the [`pulsar-admin namespace set-deduplication`](reference-pulsar-admin.md#namespace-set-deduplication) command. You can use the `--enable`/`-e` flag and specify the namespace. Here's an example with <tenant>/<namespace>:
+You can enable message deduplication on specific namespaces, regardless of the the [default](#default) for the broker, using the [`pulsar-admin namespace set-deduplication`](reference-pulsar-admin.md#namespace-set-deduplication) command. You can use the `--enable`/`-e` flag and specify the namespace. Here's an example with `<tenant>/<namespace>`:
```bash
$ bin/pulsar-admin namespaces set-deduplication \
@@ -48,7 +48,7 @@ $ bin/pulsar-admin namespaces set-deduplication \
### Disabling message deduplication {#disabling}
-You can disable message deduplication on a specific namespace using the same method shown [above](#enabling), except using the `--disable`/`-d` flag instead. Here's an example with <tenant>/<namespace>:
+You can disable message deduplication on a specific namespace using the same method shown [above](#enabling), except using the `--disable`/`-d` flag instead. Here's an example with `<tenant>/<namespace>`:
```bash
$ bin/pulsar-admin namespaces set-deduplication \
diff --git a/site2/website/versioned_docs/version-2.1.0-incubating/deploy-kubernetes.md b/site2/website/versioned_docs/version-2.1.0-incubating/deploy-kubernetes.md
index 892ee28..a2195f9 100644
--- a/site2/website/versioned_docs/version-2.1.0-incubating/deploy-kubernetes.md
+++ b/site2/website/versioned_docs/version-2.1.0-incubating/deploy-kubernetes.md
@@ -17,7 +17,7 @@ The deployment method shown in this guide relies on [YAML](http://yaml.org/) def
* A two-bookie BookKeeper cluster
* A three-node ZooKeeper cluster
* A three-broker Pulsar cluster
-* A [monitoring stack]() consisting of [Prometheus](https://prometheus.io/), [Grafana](https://grafana.com), and the [Pulsar dashboard](administration-dashboard.md)
+* A [monitoring stack](#) consisting of [Prometheus](https://prometheus.io/), [Grafana](https://grafana.com), and the [Pulsar dashboard](administration-dashboard.md)
* A [pod](https://kubernetes.io/docs/concepts/workloads/pods/pod/) from which you can run administrative commands using the [`pulsar-admin`](reference-pulsar-admin.md) CLI tool
## Setup
@@ -38,7 +38,7 @@ To get started, you'll need:
* A Google Cloud Platform account, which you can sign up for at [cloud.google.com](https://cloud.google.com)
* An existing Cloud Platform project
-* The [Google Cloud SDK](https://cloud.google.com/sdk/downloads) (in particular the [`gcloud`](https://cloud.google.com/sdk/gcloud/) and [`kubectl`]() tools).
+* The [Google Cloud SDK](https://cloud.google.com/sdk/downloads) (in particular the [`gcloud`](https://cloud.google.com/sdk/gcloud/) and [`kubectl`](https://kubernetes.io/docs/reference/kubectl/) tools).
### Create a new Kubernetes cluster