shenshichao163-oss opened a new pull request, #8204:
URL: https://github.com/apache/incubator-seata/pull/8204

   ## What this PR does
   
   Adds a **Configuration Architecture** section to 
`script/config-center/README.md` to clarify the relationship between the two 
configuration files (`application.yml` and `config.txt`) and how they relate to 
each other.
   
   ### Changes
   
   Added a new section before "Script Introduction" that includes:
   
   1. **Explanation of the two configuration files**:
      - `application.yml` — Server-side Spring Boot configuration (port, 
logging, config/registry/store type)
      - `config.txt` — Client-side transaction configuration (transport, vgroup 
mapping, store settings)
   
   2. **Architecture diagram** showing the config flow:
      - Server reads `application.yml` → connects to Config Center
      - Config Center stores `config.txt` content (pushed by scripts)
      - Client reads from Config Center
   
   3. **FAQ section** answering:
      - Where should `seata.config.nacos.data-id` be placed?
      - What does `config.txt` do?
      - Should I use `config.txt` or `application.yml`?
   
   ### Issue Link
   
   Fixes #5608
   
   ### Motivation
   
   Issue #5608 reports confusion about Seata configuration: which file goes 
where, what each config item means, and how `application.yml` and `config.txt` 
relate to each other. This PR adds clear documentation directly in the 
config-center README to address these questions.
   
   ### Checklist
   
   - [x] I have searched the issues of this repository and believe this is not 
a duplicate.
   - [x] I have checked that this modification does not cause CI to fail.
   - [x] I will sign the Apache CLA if required.


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to