Hi Jianbin and Jiangke, Thank you for the clarification. You are absolutely right that 'seata-e2e.yaml' does not prevent users from running samples locally. My previous mention of "dependency" was imprecise.
What I intended to highlight is the manual effort currently required— specifically, the need to manually execute SQL scripts and set up the environment. The goal of this proposal is to provide a "Zero Manual Setup" experience for new developers. I also fully agree with Jiangke's suggestion. I will include clear notes in the README to distinguish the purposes of 'seata-e2e.yaml' and 'docker-compose.yaml'. I will proceed with the pilot PR for your further review. Best regards, Jian Wang (WangzJi) Jiangke Wu <[email protected]> 于2025年12月27日周六 12:39写道： > > Hi Jian, > > Thank you for proposing this improvement! I agree that adding a standard > docker-compose.yaml to simplify the local setup is a great idea, especially > for users who just want to run the samples and explore Seata quickly. > > I’d also like to mention that the existing seata-e2e.yaml is primarily used > for CI/CD integration tests and does not affect local sample execution. > Users who clone the samples locally can safely ignore that file if they’re > not running integration tests. > > Your approach of providing a lightweight, pre-configured Docker Compose > setup would definitely lower the barrier for newcomers, and I’m supportive > of moving forward with your PR. Perhaps we could also add a brief note in > the sample README to clarify that seata-e2e.yaml is optional for local runs. > > Looking forward to your contribution! > > Best Regards, > Jiangke Wu(xingfudeshi) > > > On Sat, Dec 27, 2025 at 16:27 Jian Wang <[email protected]> wrote: > > > 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] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
