mirror of
https://github.com/v2fly/v2ray-core.git
synced 2025-01-17 23:06:30 -05:00
update support file
This commit is contained in:
parent
6f1ddec78c
commit
b507828d1f
21
.github/SUPPORT.md
vendored
21
.github/SUPPORT.md
vendored
@ -15,11 +15,11 @@
|
|||||||
1. 请按模板填写 issue;
|
1. 请按模板填写 issue;
|
||||||
1. 配置文件内容使用格式化代码段进行修饰(见下面的解释);
|
1. 配置文件内容使用格式化代码段进行修饰(见下面的解释);
|
||||||
1. 在提交 issue 前尝试减化配置文件(如下):
|
1. 在提交 issue 前尝试减化配置文件(如下):
|
||||||
* 删除不必要 inbound / outbound 模块;
|
1. 删除不必要 inbound / outbound 模块;
|
||||||
* 删除不必要的路由项;
|
1. 删除不必要的路由项;
|
||||||
1. 在提交 issue 前尝试确定问题所在,比如:
|
1. 在提交 issue 前尝试确定问题所在,比如:
|
||||||
* 将 socks 代理换成 http 再次观察问题是否能重现;
|
1. 将 socks 代理换成 http 再次观察问题是否能重现;
|
||||||
* 更改加密方式再次观察问题是否能重现;
|
1. 更改加密方式再次观察问题是否能重现;
|
||||||
1. 配置文件必须结构完整,即除了必要的隐私信息之外,配置文件可以直接拿来运行。
|
1. 配置文件必须结构完整,即除了必要的隐私信息之外,配置文件可以直接拿来运行。
|
||||||
|
|
||||||
**不按模板填写的 issue 将直接被关闭**
|
**不按模板填写的 issue 将直接被关闭**
|
||||||
@ -29,9 +29,11 @@
|
|||||||
在配置文件上下加入 Markdown 特定的修饰符,如下:
|
在配置文件上下加入 Markdown 特定的修饰符,如下:
|
||||||
|
|
||||||
\`\`\`javascript
|
\`\`\`javascript
|
||||||
|
|
||||||
{
|
{
|
||||||
// 配置文件内容
|
// 配置文件内容
|
||||||
}
|
}
|
||||||
|
|
||||||
\`\`\`
|
\`\`\`
|
||||||
|
|
||||||
## Way to Get Support
|
## Way to Get Support
|
||||||
@ -47,11 +49,12 @@ You may get help in the following ways:
|
|||||||
1. Please fill in the issue template.
|
1. Please fill in the issue template.
|
||||||
1. Decorate config file with Markdown formatter (See below).
|
1. Decorate config file with Markdown formatter (See below).
|
||||||
1. Try to simplify config file before submitting the issue, such as:
|
1. Try to simplify config file before submitting the issue, such as:
|
||||||
* Removing unnecessary inbound / outbound blocks.
|
1. Removing unnecessary inbound / outbound blocks.
|
||||||
* Removing unnecessary routing rules.
|
1. Removing unnecessary routing rules.
|
||||||
1. Try to determine the cause of the issue, for example:
|
1. Try to determine the cause of the issue, for example:
|
||||||
* Replacing socks inbound with http inbound to see if the issue still exists.
|
1. Replacing socks inbound with http inbound to see if the issue still exists.
|
||||||
* Changing encryption methods to see if the issue still exists.
|
1. Changing encryption methods to see if the issue still exists.
|
||||||
|
1. Config file must be structurally complete.
|
||||||
|
|
||||||
**Any issue not following the issue template will be closed immediately.**
|
**Any issue not following the issue template will be closed immediately.**
|
||||||
|
|
||||||
@ -60,7 +63,9 @@ You may get help in the following ways:
|
|||||||
Add the following Markdown decorator to config file content:
|
Add the following Markdown decorator to config file content:
|
||||||
|
|
||||||
\`\`\`javascript
|
\`\`\`javascript
|
||||||
|
|
||||||
{
|
{
|
||||||
// config file
|
// config file
|
||||||
}
|
}
|
||||||
|
|
||||||
\`\`\`
|
\`\`\`
|
||||||
|
Loading…
Reference in New Issue
Block a user