forked from ihciah/shadow-tls
-
Notifications
You must be signed in to change notification settings - Fork 0
/
docker-compose.yml
35 lines (33 loc) · 1.38 KB
/
docker-compose.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
version: '2.4'
services:
shadow-tls:
image: ghcr.io/ihciah/shadow-tls:latest
container_name: shadow-tls
restart: always
network_mode: "host"
environment:
- MODE=
- LISTEN=
- SERVER=
- TLS=
- PASSWORD=
# Available environs:
# MODE: client or server
# LISTEN: local listen address with port
# SERVER: remote address with port
# TLS: domain name in sni for client mode(like xxx.com.cn)
# shadow-tls server address with port for server mode(like xxx.com.cn:443)
# PASSWORD: shadow-tls password
# ALPN(optional): set alpns(like http/1.1, http/1.1;h2, recommend to leave it blank if you don't know it)
# THREADS(optional): set threads number(recommend to leave it blank)
# DISABLE_NODELAY(optional): disable TCP_NODELAY(recommend to leave it blank)
# FASTOPEN(optional): enable TCP_FASTOPEN
# WILDCARD_SNI: Use sni:443 as handshake server(off/authed/all)
# Note:
# Multiple SNIs is supported now.
# For full help, see https://github.com/ihciah/shadow-tls/wiki/How-to-Run#parameters
# Server side example: cloudflare.com:1.1.1.1:443;captive.apple.com;cloud.tencent.com
# Client side example: captive.apple.com;cloud.tencent.com
# If server is configured with multiple SNIs, server will extract ServerName and find
# it in mapping, then use the corresponding backend or the fallback one.
# If client is configured with multiple SNIs, client will pick one in random.