Hi Community, I have noticed that our current samples (e.g., at-sample/springboot- dubbo-seata) rely heavily on 'seata-e2e.yaml' for environment setup.
While this works effectively for our CI/CD pipelines, it creates unnecessary friction for developers who simply want to run a sample locally to explore Seata's features. To lower the barrier to entry, I propose adding a standard 'docker-compose.yaml' to our primary samples. The Plan: I will add a lightweight 'docker-compose.yaml' to each sample directory that: - Starts Infrastructure Only: Deploys MySQL (pre-initialized), Zookeeper, and Seata Server. - Requires No Building: Uses official Docker images. Pilot: I have already prepared and verified this setup for the 'at-sample/springboot-dubbo-seata' module. If there are no objections, I will proceed with a PR for this sample and potentially extend it to others. Best regards, Jian Wang (WangzJi) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
