How wang95/fxw works
Main Components
• FxW as the central repository containing all the configurations.
• Three primary nodes for each supported proxy tool:
• Clash: Contains multiple YAML configuration files (e.g., CFW-v0.10.4-bak.yaml, Clash-config.yaml, cfw-settings.yaml) and a “ruleset” directory that holds various YAML files (like OpenAI.yaml, PayPal.yaml, etc.).
• QuantumultX: Contains its own configuration files (QuantumultX.conf, Js.conf) along with subdirectories such as “filter” (lists for Apple, OpenAI, and more) and “script” (e.g., VSCO-unlock.js).
• Surge: Has its own configuration file (Surge-v4.conf), along with several subdirectories:
• “module”: Includes individual modules (e.g., Apple_Geo_Services.sgmodule, YouTube-AdBlock.sgmodule) and a nested “panel” subdirectory with additional scripts and configurations.
• “ruleset”: Contains various rule list files.
• “script”: Keeps individual Surge scripts.
Relationships Between Components
• At the top level, show the FxW repository as the central “hub.”
• Within each branch, illustrate associations such as:
Architectural Patterns and External Dependencies
• Reusability and modularity:
• The separation by proxy tool shows a modular design, where each module or ruleset can be maintained independently.
• Common elements among these configurations (e.g., similar naming patterns of rule files) that may suggest standardized filters and scripts across different platforms.
• Also denote external dependencies from the README: