Compare commits

...

5 Commits

Author SHA1 Message Date
lk29
5d2309feb5 Update README.md (#89)
fix link README.ENG.md
2022-12-13 14:31:10 +08:00
lk29
bcfd0c75ed Update README.md (#88)
Add reference on README.ENG.MD
2022-12-10 10:56:51 +08:00
lk29
cd1bc29a96 add English translate Readme.md (#87)
* add English translate Readme.md

* Update README.ENG.md
2022-11-30 17:18:25 +08:00
EpLiar
f47da12a36 Merge pull request #86 from lk29/master
add English version how to choose a v2ray plan
2022-11-30 14:34:32 +08:00
lk29
691db54d11 add English version how to choose a v2ray plan 2022-11-30 11:29:00 +05:00
3 changed files with 149 additions and 0 deletions

147
README.ENG.md Normal file
View File

@@ -0,0 +1,147 @@
#v2ray-examples
Here are some V2Ray configuration examples for reference, the content keeps pace with the times, automation scripts, etc. Please do not pull the configuration from here.
Thanks to KiriKira, the author of vTemplate, Yuluowusheng and all the developers of Project V.
## Contribution Guidelines
You are welcome to make a template for your own configuration and submit a PR.
Templates should adhere to the following standards:
- use 4 spaces for indentation
- Square (curly) brackets do not wrap
- Unneeded fields should be removed
- `log` section only leaves `loglevel`
- For `outbounds`, client side should have `proxy` and `direct`, server side should have `direct` and `block`
- Unless it is a template for a specific scenario, `geoip:private` should be routed to `direct` outbound (server configuration routes to `block` outbound)
- DNS should not appear in config files unless it is a template for a specific scenario
- `uuid` should be left blank and filled by the user.
- `domainStrategy` in `routing` remains the default, which is `AsIs`.
### Examples
<!-- Here yaml is only used for syntax highlighting, the actual content is json -->
```yaml
{
"log": {
"loglevel": "warning"
},
"routing": {},
"inbounds": [],
"outbounds": []
}
```
### client
<!-- Here yaml is only used for syntax highlighting, the actual content is json -->
```yaml
{
"log": {
"loglevel": "warning"
},
"routing": {
"domainStrategy": "AsIs",
"rules": [
{
"ip": [
"geoip:private"
],
"outboundTag": "direct",
"type": "field"
}
]
},
"inbounds": [
{
"port": 1080,
"protocol": "socks",
"settings": {
"auth": "noauth",
"udp": true
},
"tag": "socks"
}
],
"outbounds": [
{
"protocol": "vmess",
"settings": {
"vnext": [
{
"users": [
{
"id": ""
}
],
"port": 1234,
"address": "Your_IP_Address"
}
]
}
},
{
"protocol": "freedom",
"tag": "direct"
}
]
}
```
### Server
<!-- Here yaml is only used for syntax highlighting, the actual content is json -->
```yaml
{
"log": {
"loglevel": "warning"
},
"routing": {
"domainStrategy": "AsIs",
"rules": [
{
"ip": [
"geoip:private"
],
"outboundTag": "blocked",
"type": "field"
}
]
},
"inbounds": [
{
"port": 1234,
"protocol": "vmess",
"settings": {
"clients": [
{
"id": "",
}
]
}
}
],
"outbounds": [
{
"protocol": "freedom"
},
{
"protocol": "blackhole",
"tag": "blocked"
}
]
}
```
## How to choose the configuration that suits you:
![](how-to-choose/how-to-choose-a-v2ray-plan-ENG.png)
Additional Notes:<br>
Although Websocket+TLS+Web may be regarded as the best solution at this stage, it is definitely not a solution recommended for novices to try as soon as they come up, let alone the only usage of V2Ray. <br>
At the same time, you should understand that the network conditions in each region are different (mainly referring to the QoS level of different protocols), you can try all the configurations to find the most suitable one for you, try to ask as little as possible, and it is best not to ask "why do I V2Ray so slow?" Questions like that.
## at last
have fun!

View File

@@ -1,5 +1,7 @@
# v2ray-examples
![ENGLISH Here are some V2Ray configuration examples for reference](README.ENG.md)
这里是一些供参考的 V2Ray 配置示例,内容与时俱进,自动化脚本等请勿从这里拉取配置。
感谢 vTemplate 的作者 KiriKira、雨落无声和 Project V 的所有开发人员。

Binary file not shown.

After

Width:  |  Height:  |  Size: 79 KiB