We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
您好!我注意到在当前的 dae 配置文件中,节点的配置信息是以 ss:// 链接的形式呈现的。这种方式虽然简洁,但在实际使用中,尤其是当需要频繁修改加密方式、密码等参数时,显得不够直观和方便。相比之下如Clash 的配置文件格式更加清晰易读,每个节点的参数都以键值对的形式明确列出,极大地方便了用户进行编辑和维护。
dae 现在使用的节点配置文件,不方便更改 node { TEST1: 'ss://[email protected] :22/#测试1' TEST2: 'ss://[email protected] :22/#测试2' } 能否建议 dae 的配置文件可以采用类似 Clash 的节点配置格式,更容易找到编辑的地方,具体示例如下: proxies: {name: TEST1, server: 192.168.1.2, port: 22, type: ss, cipher: aes-128-gcm, password: TEST1} {name:TEST2, server: 192.168.1.3, port: 22, type: ss, cipher: aes-128-gcm, password: TEST2}
直观易读:每个节点的配置参数都以明确的键值对形式呈现,一目了然。 便于编辑:用户可以直接修改 server、port、cipher、password 等参数,无需解码 ss:// 链接。 易于维护:当节点信息发生变化时,用户可以快速定位并修改相关配置,减少出错的可能性。
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue!
Sorry, something went wrong.
No branches or pull requests
Feature Request
您好!我注意到在当前的 dae 配置文件中,节点的配置信息是以 ss:// 链接的形式呈现的。这种方式虽然简洁,但在实际使用中,尤其是当需要频繁修改加密方式、密码等参数时,显得不够直观和方便。相比之下如Clash 的配置文件格式更加清晰易读,每个节点的参数都以键值对的形式明确列出,极大地方便了用户进行编辑和维护。
Use Cases
dae 现在使用的节点配置文件,不方便更改
node {
TEST1: 'ss://[email protected] :22/#测试1'
TEST2: 'ss://[email protected] :22/#测试2'
}
能否建议 dae 的配置文件可以采用类似 Clash 的节点配置格式,更容易找到编辑的地方,具体示例如下:
proxies:
{name: TEST1, server: 192.168.1.2, port: 22, type: ss, cipher: aes-128-gcm, password: TEST1}
{name:TEST2, server: 192.168.1.3, port: 22, type: ss, cipher: aes-128-gcm, password: TEST2}
Potential Benefits
直观易读:每个节点的配置参数都以明确的键值对形式呈现,一目了然。
便于编辑:用户可以直接修改 server、port、cipher、password 等参数,无需解码 ss:// 链接。
易于维护:当节点信息发生变化时,用户可以快速定位并修改相关配置,减少出错的可能性。
The text was updated successfully, but these errors were encountered: