Aias00 opened a new issue, #1972: URL: https://github.com/apache/rocketmq-dashboard/issues/1972
### Description The remote deploy.sh path starts rocketmq-server without SPRING_PROFILES_ACTIVE or datasource environment variables. application.yml defaults to the dev profile, whose datasource is an in-memory H2 database. As a result, a remote deployment can report success while Studio instances, settings, audit records, and other control-plane metadata are lost whenever the backend container restarts. The remote path also omits STUDIO_ROCKETMQ_NAMESRV_ADDR even though Docker Compose supplies it. ### Expected behavior Remote deployments must run the production profile and use an explicitly configured persistent datasource. Required datasource settings should be validated before building or replacing the remote backend container, and the configured NameServer endpoint should be forwarded. ### Actual behavior deploy.sh silently starts the default dev profile with H2 memory storage. ### Proposed fix Require datasource URL, username, and password for server or full remote deployments; pass SPRING_PROFILES_ACTIVE=prod and the datasource plus NameServer variables to the container; document the required environment values; and add a deterministic script test that stubs external commands and verifies both validation and podman arguments. -- 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]
