Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Docker deployment method to QuickStart guide for Version 5.x #646

Merged
merged 3 commits into from
May 31, 2024

Conversation

Cindy0802
Copy link
Contributor

What is the purpose of the change

The purpose of this change is to enhance the QuickStart guide by adding a Docker deployment method specifically tailored for RocketMQ Version 5.x

Brief changelog

Add Docker deployment method to QuickStart guide for Version 5.x

:::

## 4.启动 Broker+Proxy
NameServer 成功启动后,我们启动 Broker 和 Proxy ,5.x 版本下我们建议使用 Local 模式部署,即 Broker 和 Proxy 同进程部署。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

不要建议使用Local模式部署,只是quick start可以使用local部署进行验证。

@@ -0,0 +1,260 @@
# Docker 部署 RocketMQ 5.X
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“Docker 部署 RocketMQ”即可

Comment on lines 107 to 117
## 5.工具测试消息收发
```shell
# 进入broker容器
$ docker exec -it rmqbroker bash

$ sh tools.sh org.apache.rocketmq.example.quickstart.Producer
SendResult [sendStatus=SEND_OK, msgId= ...

$ sh tools.sh org.apache.rocketmq.example.quickstart.Consumer
ConsumeMessageThread_%d Receive New Messages: [MessageExt...
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

第5节去掉吧。这里其实采用的是4.x remoting的发送

@RongtongJin RongtongJin merged commit bf7bca1 into apache:new-official-website May 31, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants