Skip to content

Commit

Permalink
support file
Browse files Browse the repository at this point in the history
  • Loading branch information
DarienRaymond committed Nov 27, 2017
1 parent 6c41efe commit 6f1ddec
Show file tree
Hide file tree
Showing 2 changed files with 66 additions and 0 deletions.
File renamed without changes.
66 changes: 66 additions & 0 deletions .github/SUPPORT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
# V2Ray 用户支持 (User Support)

**English reader please skip to the English section below**

## 获得帮助信息的途径

您可以从以下渠道获取帮助:

1. 官方网站:[v2ray.com](https://www.v2ray.com)
1. Github:[Issues](https://github.com/v2ray/v2ray-core/issues)
1. Telegram:[主群](https://t.me/projectv2ray)

## Github Issue 规则

1. 请按模板填写 issue;
1. 配置文件内容使用格式化代码段进行修饰(见下面的解释);
1. 在提交 issue 前尝试减化配置文件(如下):
* 删除不必要 inbound / outbound 模块;
* 删除不必要的路由项;
1. 在提交 issue 前尝试确定问题所在,比如:
* 将 socks 代理换成 http 再次观察问题是否能重现;
* 更改加密方式再次观察问题是否能重现;
1. 配置文件必须结构完整,即除了必要的隐私信息之外,配置文件可以直接拿来运行。

**不按模板填写的 issue 将直接被关闭**

## 格式化代码段

在配置文件上下加入 Markdown 特定的修饰符,如下:

\`\`\`javascript
{
// 配置文件内容
}
\`\`\`

## Way to Get Support

You may get help in the following ways:

1. Office Site: [v2ray.com](https://www.v2ray.com)
1. Github: [Issues](https://github.com/v2ray/v2ray-core/issues)
1. Telegram: [Main Group](https://t.me/projectv2ray)

## Github Issue Rules

1. Please fill in the issue template.
1. Decorate config file with Markdown formatter (See below).
1. Try to simplify config file before submitting the issue, such as:
* Removing unnecessary inbound / outbound blocks.
* Removing unnecessary routing rules.
1. Try to determine the cause of the issue, for example:
* Replacing socks inbound with http inbound to see if the issue still exists.
* Changing encryption methods to see if the issue still exists.

**Any issue not following the issue template will be closed immediately.**

## Code formatter

Add the following Markdown decorator to config file content:

\`\`\`javascript
{
// config file
}
\`\`\`

0 comments on commit 6f1ddec

Please sign in to comment.