Hi Jian Wang, I didn't quite understand why the E2E configuration would affect users who simply want to run the samples locally. For those users who are just interested in running the examples on their own machines, they typically only need to modify a few configuration items—such as the MySQL connection details—and this is no different from how things worked before the Seata samples started using E2E. If your intention is merely to provide a basic environment (e.g., MySQL, ZooKeeper, etc.) for users running the samples locally, then I agree with your suggestion. However, I still believe this has no real connection to a "severe dependency" on seata-e2e. The E2E setup is primarily designed for verifying in GitHub CI that our samples—and their dependent resources like MySQL, Nacos, etc.—behave as expected. It doesn't imply that users need to leverage E2E capabilities when running the samples themselves.
Best Regards. Jianbin Chen, github-id: funky-eyes Jian Wang <[email protected]> 于 2025年12月27日周六 16:27写道： > 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] > >
