lizhimins opened a new pull request, #655: URL: https://github.com/apache/rocketmq-dashboard/pull/655
## Summary - Add `deploy/rocketmq/`: build an image from the Apache RocketMQ develop branch source (multi-stage Dockerfile, `build.sh` auto-selects Aliyun mirrors for apt/Maven when running in China) and launch a local test cluster via docker compose: NameServer + 2 Brokers (cluster `rocketmq-studio`, brokers `rocketmq-studio-0/1`, 1C2G each) + Proxy (remoting 8080 / gRPC 8081). - Message trace enabled end to end: brokers set `traceOn=true` / `traceTopicEnable=true`; bundled producer/consumer containers send and receive at 1 TPS through the proxy with `enableMsgTrace=true` and message keys, so `RMQ_SYS_TRACE_TOPIC` always has live trace data for Studio debugging. - Add `.claude/skills/deploy-rocketmq` skill: step-by-step deployment guide plus verified `mqadmin` usage for `clusterList`, `queryMsgByUniqueKey`, `queryMsgTraceById`, and `queryMsgByKey`. ## Test plan - [x] `./build.sh` builds `apache-rocketmq:develop` from the develop branch (Aliyun mirror auto-detection verified in a CN environment) - [x] `docker compose up -d` brings up all 6 containers; `clusterList` shows both brokers ACTIVATED under `rocketmq-studio` - [x] Producer logs continuous `SEND_OK` at 1 TPS and consumer consumes matching messages via `proxy:8080` - [x] `queryMsgByUniqueKey` / `queryMsgTraceById` / `queryMsgByKey` all return expected data, including Pub/Sub trace records - [x] Fresh redeploy (`docker compose down -v && up -d`) verified end to end -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
