config file draft
See original GitHub issueHi, here’s a very basic config file template designed to work with pproxy
. I’m open for all sorts of feedback and improvement as this probably covers ~60 percent of what pproxy
offers.
{
"general":{
"block":{
"enabled": true,
"type": "path_list/regex_list",
"values": [
"1.1.1.1/24",
"2.2.2.2/24",
"in case of path_list => /path/to/the/file1",
"in case of path_list => /path/to/the/file2"
]
},
"check_alive":{
"enabled": true,
"interval": 30
},
"schedule":{
"enabled":true,
"algorithm": "fa"
},
"pac":{
"enabled": true,
"path": "asdasds"
},
"sys":{
"enabled": true
},
"test":{
"enabled": true,
"path": "http://ident.me"
}
},
"servers":[
{
"enabled": true,
"name": "SERVER1",
"type": "in/out",
"addr": "0.0.0.0",
"port": "80",
"unix_socket": "/tmp/myproxy",
"inverse": false,
"http_settings":{
"enabled": true,
"disable_http_connect": true,
"auth": {
"enabled": true,
"creds": [
"user1:pass1",
"user2:pass2"
]
},
"ssl": {
"enabled": true,
"type": "base64/path/insecure",
"cert": "asdasdasd",
"key": "asdasdasd"
}
},
"socks_settings":{
"enabled":true,
"version": "4/5/4+5",
"auth": {
"enabled": true,
"creds": [
"user1:pass1",
"user2:pass2"
]
},
"ssl": {
"enabled": true,
"type": "base64/path/insecure",
"cert": "asdasdasd",
"key": "asdasdasd"
}
},
"ss_settings":{
"enabled": true,
"password": "123",
"cipher": "aes-256-gcm",
"ssl": {
"enabled": true,
"type": "base64/path/insecure",
"cert": "asdasdasd",
"key": "asdasdasd"
}
},
"ssr_settings":{
"enabled":true,
"password": "123",
"cipher": "aes-256-gcm",
"plugins":{
"enabled": true,
"values":[
"plain",
"origin",
"http_simple",
"tls1.2_ticket_auth",
"verify_simple",
"verify_deflate"
]
}
},
"redir_settings":{
"enabled": true
},
"tunnel_settings":{
"enabled": true,
"hosts": ["www.google.com"]
},
"ssh_settings":{
"enabled": true,
"remote_host": "1.2.3.4",
"remote_port": 22,
"cred_type": "password/key_path/key_base64",
"username": "root",
"cred": "whatever"
},
"ws_settings":{
"enabled": true,
"ssl": {
"enabled": true,
"type": "base64/path/insecure",
"cert": "asdasdasd",
"key": "asdasdasd"
}
}
}
]
}
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Configuration File Format (Draft) - V2Fly.org
This configuration format is designed to replace the previous version of configuration format. Currently this format is in the drafting phase, and may...
Read more >Configuration (DRAFT) — Python 3.6.1 documentation
This is a draft for a new API. ... Configuration files are useful if you want to enable non-programmers to configure your application, ......
Read more >Configuration (DRAFT) — Bottle 0.13-dev documentation
Configuration (DRAFT)¶ ... This is a draft for a new API. Tell us what you think. Bottle applications can store their configuration in...
Read more >Configuration
The configuration of the @PLUGIN@ plugin is done in the gerrit.config file. This plugin overloads Gerrit own DRAFT workflow. The WIP workflow can...
Read more >Configuration files — JAGGER - Admin Guide Draft 1.0 ...
There are a few config files used by JAGGER and they're stored in /opt/rr3/application/config/ folder. config.php¶. This is standard config file for codeigniter ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
couple of points:
json
instead ofyaml
(#45) because I didn’t want to introduce a new dependencyForget shadowsocks. We config like this:
arg=( ‘-l’,‘socks5://127.0.0.1:8080’, ‘-r’,‘ss://cipher:key@127.0.0.1:8000’, ) pproxy.server.main(args)
Isn’t it cool?