# 多机场订阅

建议使用UI配置：\[首页]->\[通用]->\[代理服务器]->\[新增策略组]->\[使用外部代理列表]->\[粘贴订阅或者本地节点文件（带后缀名）]

编辑配置文件：

配置方案1: 

`[Proxy Group]` \
`Proxy = select, 机场1, 机场2, 机场3, 聚合 机场1 = select, policy-path=机场1的Surge托管配置 机场2 = select, policy-path=机场2的Surge托管配置 机场3 = select, policy-path=机场3的Surge托管配置 聚合 = select, include-other-group="机场1, 机场2, 机场3", policy-regex-filter=节点筛选(比如:HK|HONGKONG|香港)`<br>

配置方案2(隐藏机场的策略): \
`[Proxy Group]` \
`Proxy = select, 聚合 机场1 = select, policy-path=机场1的Surge托管配置, hidden=true 机场2 = select, policy-path=机场2的Surge托管配置, hidden=true 机场3 = select, policy-path=机场3的Surge托管配置, hidden=true 聚合 = select, include-other-group="机场1, 机场2, 机场3", policy-regex-filter=节点筛选(比如:HK|HONGKONG|香港)`

**举例：**\
`[Proxy Group]` \
\
`所有机场合集 = select,Flower cloud，TAG，CTC , update-interval=0, no-alert=0, hidden=0, include-all-proxies=0` \
\
`Flower cloud = select, policy-path=Flower.conf, update-interval=0, no-alert=0, hidden=0, include-all-proxies=0` \
\
`TAG = select, policy-path=TAG.conf, update-interval=0, no-alert=0, hidden=0, include-all-proxies=0` \
\
`CTC = select, policy-path=CTC.conf, update-interval=0, no-alert=0, hidden=0, include-all-proxies=0`

<div><figure><img src="/files/tMcb4YCYzrIKMbM49GsQ" alt=""><figcaption></figcaption></figure> <figure><img src="/files/Sgpj1JlWQl9UwYYMX68U" alt=""><figcaption></figcaption></figure> <figure><img src="/files/dkOUqmmneUAbqCN1W1P2" alt=""><figcaption></figcaption></figure></div>

也可通过Sub-Store第三方工具处理多机场订阅。\ <br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.surge.community/basic/duo-ji-chang-ding-yue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.