You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@seata.apache.org by "shenshichao163-oss (via GitHub)" <gi...@apache.org> on 2026/08/15 15:07:44 UTC
[PR] docs: add configuration architecture section to config-center README [incubator-seata]
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: notifications-unsubscribe@seata.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org
Re: [PR] docs: add configuration architecture section to config-center README [incubator-seata]
Posted by "Copilot (via GitHub)" <gi...@apache.org>.
Copilot commented on code in PR #8204:
URL: https://github.com/apache/incubator-seata/pull/8204#discussion_r3843605608
##########
script/config-center/README.md:
##########
@@ -30,6 +30,77 @@ you only need to follow the instructions below and keep the corresponding config
| store.db.user | service.vgroupMapping.default_tx_group |
| store.db.password | service.disableGlobalTransaction |
+## Configuration Architecture
+
+Before using these scripts, it is important to understand the Seata configuration architecture:
+
+### Two Configuration Files
+
+Seata uses two distinct configuration files:
+
+1. **`server/src/main/resources/application.yml`** — The Seata **server** configuration file (Spring Boot style). It contains:
+ - Server port, logging, and Spring application settings
+ - `seata.config.type` — Where the server reads its configuration from (`file`, `nacos`, `consul`, `apollo`, `zk`, `etcd3`)
+ - `seata.registry.type` — Where the server registers itself for service discovery (`file`, `nacos`, `eureka`, `redis`, `zk`, `consul`, `etcd3`, `sofa`, `seata`)
+ - `seata.store.mode` — Transaction log storage mode (`file`, `db`, `redis`, `raft`)
Review Comment:
The documentation points to `server/src/main/resources/application.yml`, which is a source-tree path; the issue this PR targets is about the *server distribution* where the file is typically `conf/application.yml`. Also, the supported `seata.config.type` / `seata.registry.type` values here are incomplete (e.g., `custom` and `springCloudConfig` are valid config types; `raft`/`custom` are valid registry types).
This issue also appears in the following locations of the same file:
- line 47
- line 71
- line 92
--
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: notifications-unsubscribe@seata.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org