This is an automated email from the ASF dual-hosted git repository.
gongchao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hertzbeat.git
The following commit(s) were added to refs/heads/master by this push:
new aaf3cf09c [docs] fix several typos in docs (#2047)
aaf3cf09c is described below
commit aaf3cf09c2e527b13089a845d5454d520b0385f9
Author: lwyang <[email protected]>
AuthorDate: Thu May 30 08:29:24 2024 +0800
[docs] fix several typos in docs (#2047)
Co-authored-by: tomsun28 <[email protected]>
---
home/docs/introduce.md | 2 +-
home/docs/start/upgrade.md | 4 ++--
home/versioned_docs/version-v1.4.x/introduce.md | 2 +-
home/versioned_docs/version-v1.4.x/start/upgrade.md | 4 ++--
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/home/docs/introduce.md b/home/docs/introduce.md
index 537046697..d559fa6ca 100644
--- a/home/docs/introduce.md
+++ b/home/docs/introduce.md
@@ -103,7 +103,7 @@ Do you believe that users can just write a monitoring
template on the UI page, c
### No Agent Required
-> For users who have used various systems, the most troublesome thing is the
installation, deployment, debugging and upgrading of various `agents'.
+> For users who have used various systems, the most troublesome thing is the
installation, deployment, debugging and upgrading of various `agents`.
> You need to install one `agent` per host, and several corresponding `agents`
> to monitor different application middleware, and the number of monitoring
> can easily reach thousands, so writing a batch script may ease the burden.
>
> The problem of whether the version of `agent` is compatible with the main
> application, debugging the communication between `agent` and the main
> application, upgrading the `agent` synchronization and so on and so forth,
> are all big headaches.
diff --git a/home/docs/start/upgrade.md b/home/docs/start/upgrade.md
index 0437d14e4..917b8ffbe 100644
--- a/home/docs/start/upgrade.md
+++ b/home/docs/start/upgrade.md
@@ -26,12 +26,12 @@ Apache HertzBeat (incubating)'s metadata information is
stored in H2 or Mysql, P
2. If using the built-in default H2 database
- Need to mount or back up `-v $(pwd)/data:/opt/hertzbeat/data` database
file directory in the container `/opt/hertzbeat/data`
- Stop and delete the container, delete the local HertzBeat docker image,
and pull the new version image
- - Refer to [Docker installation of HertzBeat] (docker-deploy) to create a
new container using a new image. Note that the database file directory needs to
be mounted `-v $(pwd)/data:/opt/hertzbeat/data`
+ - Refer to [Docker installation of HertzBeat](docker-deploy) to create a
new container using a new image. Note that the database file directory needs to
be mounted `-v $(pwd)/data:/opt/hertzbeat/data`
3. If using external relational database Mysql, PostgreSQL
- No need to mount the database file directory in the backup container
- Stop and delete the container, delete the local HertzBeat docker image,
and pull the new version image
- - Refer to [Docker installation HertzBeat] (docker-deploy) to create a new
container using the new image, and configure the database connection in
`application.yml`
+ - Refer to [Docker installation HertzBeat](docker-deploy) to create a new
container using the new image, and configure the database connection in
`application.yml`
### Upgrade For Package Deploy
diff --git a/home/versioned_docs/version-v1.4.x/introduce.md
b/home/versioned_docs/version-v1.4.x/introduce.md
index c54423d32..a72703e6a 100644
--- a/home/versioned_docs/version-v1.4.x/introduce.md
+++ b/home/versioned_docs/version-v1.4.x/introduce.md
@@ -105,7 +105,7 @@ Do you believe that users can just write a monitoring
template on the UI page, c
### No Agent Required
-> For users who have used various systems, the most troublesome thing is the
installation, deployment, debugging and upgrading of various `agents'.
+> For users who have used various systems, the most troublesome thing is the
installation, deployment, debugging and upgrading of various `agents`.
> You need to install one `agent` per host, and several corresponding `agents`
> to monitor different application middleware, and the number of monitoring
> can easily reach thousands, so writing a batch script may ease the burden.
>
> The problem of whether the version of `agent` is compatible with the main
> application, debugging the communication between `agent` and the main
> application, upgrading the `agent` synchronization and so on and so forth,
> are all big headaches.
diff --git a/home/versioned_docs/version-v1.4.x/start/upgrade.md
b/home/versioned_docs/version-v1.4.x/start/upgrade.md
index 1c602dba4..6836d8a62 100644
--- a/home/versioned_docs/version-v1.4.x/start/upgrade.md
+++ b/home/versioned_docs/version-v1.4.x/start/upgrade.md
@@ -27,12 +27,12 @@ HertzBeat's metadata information is stored in H2 or Mysql,
PostgreSQL relational
2. If using the built-in default H2 database
- Need to mount or back up `-v $(pwd)/data:/opt/hertzbeat/data` database
file directory in the container `/opt/hertzbeat/data`
- Stop and delete the container, delete the local HertzBeat docker image,
and pull the new version image
- - Refer to [Docker installation of HertzBeat] (docker-deploy) to create a
new container using a new image. Note that the database file directory needs to
be mounted `-v $(pwd)/data:/opt/hertzbeat/data`
+ - Refer to [Docker installation of HertzBeat](docker-deploy) to create a
new container using a new image. Note that the database file directory needs to
be mounted `-v $(pwd)/data:/opt/hertzbeat/data`
3. If using external relational database Mysql, PostgreSQL
- No need to mount the database file directory in the backup container
- Stop and delete the container, delete the local HertzBeat docker image,
and pull the new version image
- - Refer to [Docker installation HertzBeat] (docker-deploy) to create a new
container using the new image, and configure the database connection in
`application.yml`
+ - Refer to [Docker installation HertzBeat](docker-deploy) to create a new
container using the new image, and configure the database connection in
`application.yml`
### Upgrade For Package Deploy
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
