feat: publish generic Telegram WEB proxy stack

This commit is contained in:
Maintainer
2026-10-14 16:37:48 +07:00
commit a91a7ca11a
14 changed files with 1153 additions and 0 deletions
+61
View File
@@ -0,0 +1,61 @@
name: telegram-web-proxy
services:
proxy:
build:
context: .
dockerfile: Dockerfile
args:
TPROXY_COMMIT: c8adb8b7c6b7fc46c12ae3acb68be9070c26a8e8
TPROXY_SHA256: a78b48f536180143dd7005785ca397310c36ee0b132e19949a45d64f586ab549
MTPROXY_COMMIT: f36d8af769ffaeac36978d38c2c0f6d1104c2137
MTPROXY_SHA256: 919795c416b870670841a21d1930ad97a24c7b84b9eb8c6f9e3de32f2fdf4655
image: telegram-web-proxy:local
container_name: tg-web-proxy
restart: unless-stopped
environment:
TPROXY_HOSTNAME: ${TPROXY_HOSTNAME:?set by install.sh}
MTPROXY_PUBLIC_IP: ${MTPROXY_PUBLIC_IP:?set by install.sh}
MTPROXY_WORKERS: ${MTPROXY_WORKERS:-1}
MTPROXY_MAX_CONNECTIONS: ${MTPROXY_MAX_CONNECTIONS:-4096}
volumes:
- tg_webproxy_data:/data
networks:
- npm_network
expose:
- "8088"
cap_drop:
- ALL
cap_add:
- SETUID
- SETGID
security_opt:
- no-new-privileges:true
pids_limit: 256
mem_limit: 768m
cpus: 1.25
healthcheck:
test:
- CMD-SHELL
- >-
curl -fsS http://127.0.0.1:8081/readyz >/dev/null &&
curl -fsS -H "Host: $${TPROXY_HOSTNAME}"
http://127.0.0.1:8088/ >/dev/null
interval: 30s
timeout: 5s
retries: 3
start_period: 60s
logging:
driver: json-file
options:
max-size: "10m"
max-file: "3"
volumes:
tg_webproxy_data:
name: tg_webproxy_data
networks:
npm_network:
external: true
name: ${NPM_NETWORK_NAME:?set by install.sh}