[Studio] feat: add MySQL persistence and the deployment it needs - #796
Merged
lizhimins merged 1 commit intoAug 3, 2026
Merged
Conversation
Studio kept everything in memory, so topics, groups, settings, audit records and query history were lost on restart. - MyBatis-Plus + MySQL 8.0 with a single authoritative schema (9 tables) and sample data for an e-commerce trade flow - entities, mappers and a MyBatis-Plus backed settings repository - OperationAuditService records mutations, wired into settings and audit - compose runs MySQL alongside the server, pinned to Asia/Shanghai with an explicit UTF-8 JDBC connection - attach MySQL to the rocketmq network and drop the nginx runtime resolver: under podman the first DNS answers NXDOMAIN, which broke the datasource and caused sporadic 502s on /api
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Studio kept everything in memory, so topics, groups, settings, audit records
and query history were lost on restart.
sample data for an e-commerce trade flow
explicit UTF-8 JDBC connection
under podman the first DNS answers NXDOMAIN, which broke the datasource and
caused sporadic 502s on /api