Skip to content

support remote YAML parsers(part) of CFW#434

Open
GkingF wants to merge 7 commits intoMetaCubeX:mainfrom
GkingF:main
Open

support remote YAML parsers(part) of CFW#434
GkingF wants to merge 7 commits intoMetaCubeX:mainfrom
GkingF:main

Conversation

@GkingF
Copy link

@GkingF GkingF commented Feb 1, 2025

support remote YAML parsers(prepend-proxies,prepend-proxy-groups,prepend-rules) of CFW

@abao-chen
Copy link

请问下怎么使用呀?在订阅链接里parsers=YmlUrl(url)好像不行,订阅链接里只能接受http格式

@myacera100
Copy link

尝试在订阅链接后面加入?parsers=https://github.com/xxx/parsers.yaml,并且在更新前开启了日志,更新后自定义规则并未生效,且未发现parsers相关的日志输出。求指教

@GkingF
Copy link
Author

GkingF commented Feb 5, 2026

请问下怎么使用呀?在订阅链接里parsers=YmlUrl(url)好像不行,订阅链接里只能接受http格式

一个简单的demo,以wireguard节点作为例子

该例子会在节点列表最前增加一个wireguard-peer节点,并创建一个名为Home的代理组,包含wireguard-peer和DIRECT两个选项。
其余的代理类型也是同理,只需将type和相关字段替换为对应的代理类型即可。
可以将该配置文件上传到github gist中,可以得到gist链接,例如:
https://gist.githubusercontent.com/GkingF/xxx/raw/wireguard.yml
将其进行urlEncode后:
https%3A%2F%2Fgist.githubusercontent.com%2FGkingF%2Fxxx%2Fraw%2Fwireguard.yml
拼接至订阅链接之后:
https://sub.dev/sub?target=clash&parsers=https%3A%2F%2Fgist.githubusercontent.com%2FGkingF%2Fxxx%2Fraw%2Fwireguard.yml

parsers:
  yaml:
    prepend-proxies:
      - name: "wireguard-peer"
        type: "wireguard"
        private-key: "private-key"
        server: "server.addr"
        port: 55820
        ip: "198.18.7.4"
        public-key: "public-key"
        persistent-keepalive: 25
    prepend-proxy-groups:
      - name: "Home"
        type: "select"
        proxies:
          - "wireguard-peer"
          - "DIRECT"
    prepend-rules:
      - IP-CIDR,192.168.2.0/24,Home
      - IP-CIDR,198.18.7.0/24,Home

@GkingF
Copy link
Author

GkingF commented Feb 5, 2026

尝试在订阅链接后面加入?parsers=https://github.com/xxx/parsers.yaml,并且在更新前开启了日志,更新后自定义规则并未生效,且未发现parsers相关的日志输出。求指教

?parsers=https://github.com/xxx/parsers.yaml

https://github.com/xxx/parsers.yaml
这个链接URLEncode一下就可以了

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants