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: [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