This is an automated email from the ASF dual-hosted git repository.
popduke pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/bifromq.git
The following commit(s) were added to refs/heads/main by this push:
new 6f32e4d8 1. fix link error in README; (#153)
6f32e4d8 is described below
commit 6f32e4d8f1b52ca2c9136576bbf0b2ee0a9d297b
Author: Gu Jiawei <[email protected]>
AuthorDate: Tue Jul 15 15:48:16 2025 +0800
1. fix link error in README; (#153)
2. remove unused email address.
---
.github/ISSUE_TEMPLATE/bug_report.md | 9 +++------
README.md | 2 +-
README.zh_Hans.md | 4 ++--
3 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md
b/.github/ISSUE_TEMPLATE/bug_report.md
index ab05893d..66972b6c 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -36,10 +36,8 @@ OR
**Issues that only describe symptoms without providing either of the above may
not contain enough valuable data for
problem identification and are unlikely to receive a response from the team.**
-If you cannot meet either of these requirements, please contact
[email](mailto:[email protected]) for paid consulting
-services.
-Alternatively, we encourage you to help troubleshooting and submit a Pull
Request with an Issue Fix to become an
-external [contributor](https://github.com/bifromqio/bifromq/blob/main/CLA.md)
to BifroMQ.
+We encourage you to help troubleshooting and submit a Pull Request with an
Issue Fix to become a
+[contributor](https://bifromq.apache.org/docs/contribution_guide/intro/) to
BifroMQ.
## ⚠️ *重要提示：提交问题前请仔细阅读*
@@ -64,8 +62,7 @@ external
[contributor](https://github.com/bifromqio/bifromq/blob/main/CLA.md) to
**仅描述现象而不提供上述两项中任意一项的问题报告，通常无法为问题定位提供足够有价值的信息，因此可能不会得到团队的响应。**
-如果您无法满足这两项要求中的任何一项，请联系[邮箱](mailto:[email protected])
获取付费咨询服务。另外，我们也鼓励您能帮助定位问题，提交解决问题的
-Pull Request，成为 BifroMQ
的[外部贡献者](https://github.com/bifromqio/bifromq/blob/main/CLA.md)。
+我们鼓励您能帮助定位问题，提交解决问题的 Pull Request，成为 BifroMQ
的[贡献者](https://bifromq.apache.org/docs/contribution_guide/intro/)。
### **Describe the bug**
diff --git a/README.md b/README.md
index e6bfab1b..1b84ceec 100644
--- a/README.md
+++ b/README.md
@@ -42,7 +42,7 @@ docker run -d -m <MEM_LIMIT> -e
MEM_LIMIT='<MEM_LIMIT_IN_BYTES>' --name bifromq
Substitute `<MEM_LIMIT>` and `<MEM_LIMIT_IN_BYTES>` with the actual memory
allocation for the Docker process, for
example, `2G` for `<MEM_LIMIT>` and `2147483648` for `<MEM_LIMIT_IN_BYTES>`.
If not specified, BifroMQ defaults to using
the hosting server's physical memory for determining JVM parameters. This can
result in the Docker process being
-terminated by the host's Out-of-Memory (OOM) Killer. Refer to
[here](https://bifromq.io/docs/installation/docker/)
+terminated by the host's Out-of-Memory (OOM) Killer. Refer to
[here](https://bifromq.apache.org/docs/installation/docker/)
for more information.
You can build a BifroMQ cluster using Docker Compose on a single host for
development and testing. Suppose you want to create a cluster with three nodes:
node1,
diff --git a/README.zh_Hans.md b/README.zh_Hans.md
index e1902c50..217ec19c 100644
--- a/README.zh_Hans.md
+++ b/README.zh_Hans.md
@@ -34,7 +34,7 @@ docker run -d -m <MEM_LIMIT> -e
MEM_LIMIT='<MEM_LIMIT_IN_BYTES>' --name bifromq
将`<MEM_LIMIT>`和`<MEM_LIMIT_IN_BYTES>`替换为 Docker
进程的实际内存分配，例如，使用`2G`替换`<MEM_LIMIT>`，使用 `2147483648`
替换`<MEM_LIMIT_IN_BYTES>`。如果未指定这些值，BifroMQ 默认使用宿主服务器的物理内存来确定JVM参数。这可能导致 Docker
-进程被宿主机的OOM
Killer终止，更多供信息[参考](https://bifromq.apache.org/zh-Hans/docs/installation/docker/)。
+进程被宿主机的OOM
Killer终止，更多供信息[参考](https://bifromq.apache.org/docs/installation/docker/)。
你可以使用Docker Compose在单个host上搭建BifroMQ集群用于开发和测试。假设你想创建一个包含三个节点的集群：node1、node2 和
node3，目录结构如下：
```
@@ -202,7 +202,7 @@ MQTT Broker 实例，确保高可用性。 你也可以通过添加更多的节
独立工作负载集群部署模式旨在构建大规模的，多租户的 Serverless
集群。在这种模式下，集群由几个专门的子集群组成，每个子集群都专注于一个特定的'独立类型'的工作负载。这些子集群共同协作形成一个逻辑的
-MQTT Broker
实例。这是最复杂的部署模式，需要额外的非开源协作组件。如需商业支持，请与我们[联系](mailto:[email protected])。
+MQTT Broker 实例。这是最复杂的部署模式，需要额外的非开源协作组件。
## 用户社区
