Configuration¶
Subcon reads conf/pref.toml on startup (or the path supplied by --pref). When
a relative path is missing, Subcon also checks /etc/subcon.
Most behavior is driven by three layers: config, profiles, and schema.
graph TD
A[pref.toml] --> B[Profile paths]
B --> C[Schema registry]
C --> D[Targets: Clash / Surge]
File map¶
| Path | Role |
|---|---|
conf/pref.toml |
Global settings and feature switches. |
conf/profiles/ |
Local proxy lists. |
conf/base/ |
Target base templates. |
conf/snippets/ |
Proxy groups and rulesets. |
conf/rules/ |
Rule list files referenced by rulesets. |
schema/ |
Protocol schemas and target mapping. |
On Debian packages, these directories are installed under /etc/subcon.
Configuration checklist¶
- Ensure
common.schemapoints toschema/. - Point base templates to
conf/base/*. - Set
network.allowed_domainif you will useurl. - Verify
server.listenandserver.port.
Note
The docs in this section only cover fields used by Subcon. Extra keys are ignored.