Updated Configuration (markdown)

Sanaei
2026-04-21 20:18:10 +02:00
parent 6408b1c65f
commit 587d86708d

@@ -382,4 +382,12 @@ The Geosites in Xray-core play a key role in traffic routing, enabling flexible
2. Open `Geofiles` dropdown and update the needed geofile
![image](https://github.com/user-attachments/assets/6765b54d-3858-4fd3-b75b-17b5bc2b983f)
![image](https://github.com/user-attachments/assets/6765b54d-3858-4fd3-b75b-17b5bc2b983f)
## Custom GeoSite / GeoIP DAT sources
Administrators can add custom GeoSite and GeoIP `.dat` files from URLs in the panel (same workflow as updating built-in geofiles). Files are stored under the same directory as the Xray binary (`XUI_BIN_FOLDER`, default `bin/`) with deterministic names: `geosite_<alias>.dat` and `geoip_<alias>.dat`.
**Routing:** Xray resolves extra lists using the `ext:` form, for example `ext:geosite_myalias.dat:tag` or `ext:geoip_myalias.dat:tag`, where `tag` is a list name inside that DAT file (same pattern as built-in regional files such as `ext:geoip_IR.dat:ir`).
**Reserved aliases:** Only for deciding whether a name is reserved, the panel compares a normalized form of the alias (`strings.ToLower`, `-` → `_`). User-entered aliases and generated file names are not rewritten in the database; they must still match `^[a-z0-9_-]+$`. For example, `geoip-ir` and `geoip_ir` collide with the same reserved entry.