unbridled-41 opened a new pull request, #5439: URL: https://github.com/apache/rocketmq-dashboard/pull/5439
## Problem / Evidence `CONTRIBUTING.md:40` says that after the documented full-stack command the studio is available at `<http://127.0.0.1:6789>` (frontend) **and** `<http://127.0.0.1:8888>` (backend). The backend port is never published to the host: ``` $ docker compose -f deploy/docker-compose.yml config mysql: published 3306 rocketmq-web: published 6789 rocketmq-server: expose 8888 # no host mapping ``` - `deploy/docker-compose.yml:93-94` — `expose: - "8888"`, and no `ports:` entry for `rocketmq-server`. - `deploy/nginx.conf` proxies `location /api/` → `http://rocketmq-server:8888`, so the API *is* reachable — through 6789. Reproduction: run the CONTRIBUTING full-stack command, then `curl http://127.0.0.1:8888/actuator/health` → connection refused, while `http://127.0.0.1:6789/api/...` works. The 8888 URL is correct in the other places it appears — `docs/ai-agent-architecture.md` describes registering the MCP server when the backend is started directly, which is exactly the "Run the backend only" section (`mvn spring-boot:run`) that binds 8888 on the host. ## Root cause / Fix The sentence was written before the compose stack moved to Nginx-only host exposure. Correct it to say the API is served through 6789, that 8888 is container-internal, and that the 8888 URL applies when the backend runs directly. Apply the same clarification to the port line in `README.md` / `README_zh.md`, which lists 8888 without qualification. ## Priority & scoring PRIORITY 62 = 影响 14 (a documented URL fails for every contributor following the section; the working entry point is not stated) + 波及 10 (CONTRIBUTING + both READMEs) + 可复现 20 (verified with `docker compose config` and the missing `ports` mapping) + 维护价值 18 (three documents stop contradicting the compose file). FIX_CONFIDENCE 80: a documentation-only correction; publishing 8888 instead would be a deployment-design change and is deliberately not done. ## Tests Documentation-only; verified against the resolved compose configuration (`docker compose config`, shown above) and `deploy/nginx.conf`'s `/api/` proxy target. No port, manifest or script changes. ## Risk None. -- 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]
