yuluo-yx opened a new issue, #2692:
URL: https://github.com/apache/rocketmq-dashboard/issues/2692

   ## Problem\n\nThe remote deployment path documents environment variables 
that are not applied consistently:\n\n1. PUBLIC_PORT is used by deploy.sh for 
verification, but Docker Compose publishes a hard-coded port 6789.\n2. 
deploy.sh loads deploy/.env locally and packages it under deploy/.env remotely, 
while the prerequisite check and Compose startup require a different root .env 
file.\n3. MAVEN_CACHE_DIR is documented, but remote settings lookup and the 
Maven volume remain hard-coded to the remote user home cache.\n\nThese 
mismatches make a first deployment following the documentation fail, make 
custom frontend ports fail verification, and silently ignore custom Maven cache 
locations.\n\n## Reproduction\n\n- Set PUBLIC_PORT=18080 and render 
deploy/docker-compose.yml; the published port remains 6789.\n- Follow 
deploy/README.md with only deploy/.env present; the script rejects the missing 
remote root .env before upload.\n- Set MAVEN_CACHE_DIR to another absolute 
path; inspect remote 
 Docker arguments and observe the home .m2 mount.\n\n## Expected 
behavior\n\nThe local deploy/.env should be the single deployment configuration 
source and be used from its packaged remote location. PUBLIC_PORT should 
control both Compose publication and verification. MAVEN_CACHE_DIR should 
consistently control settings lookup, repository storage, and volume 
mounting.\n\n## Scope\n\nKeep changes within deploy configuration, 
documentation, the remote deployment script, and an offline command-contract 
test. Do not start containers or contact a real remote host during tests.\n\n## 
Evidence\n\nVerified on rocketmq-studio at 
899561e56c50d3356cd32caa88f08d80e469eed1.


-- 
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]

Reply via email to