-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdocker-compose.client-watch.yml
More file actions
53 lines (49 loc) · 1.73 KB
/
Copy pathdocker-compose.client-watch.yml
File metadata and controls
53 lines (49 loc) · 1.73 KB
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
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
# RpcNode client-watch — CDN host. Hourly GitHub vs catalog pin.
# Telegram token/chat come from FetchClients (PUT /api/v1/telegram), not from this file.
# State volume survives image rebuild. Do not `down -v` if you want to keep Telegram.
#
# network_mode: bridge = docker0, no new subnet, no compose aliases
# (avoids "address pools fully subnetted" and "aliases only on user-defined networks").
# default network is the existing `none` so compose does not allocate a pool.
#
# docker compose -f docker-compose.client-watch.yml up -d --build --pull never
# FetchClients → Настройки: http://<этот-хост>:8094
#
# Open TCP 8094 on the host yourself. This file does not touch ufw.
name: rpcnode-client-watch
services:
client-watch:
image: rpcnode-client-watch:local
pull_policy: build
build:
context: ./tools/client-watch
dockerfile: Dockerfile
pull: false
container_name: rpcnode-client-watch
restart: unless-stopped
network_mode: bridge
ports:
- "${CLIENT_WATCH_PORT:-8094}:8094"
env_file:
- client-watch.env
environment:
CLIENT_WATCH_LISTEN: "0.0.0.0:8094"
CLIENT_WATCH_CATALOG: /data/clients/catalog.json
CLIENT_WATCH_CLIENTS: /data/clients
CLIENT_WATCH_STATE: /var/lib/client-watch/state.json
CLIENT_WATCH_INTERVAL: ${CLIENT_WATCH_INTERVAL:-1h}
volumes:
- ${CLIENT_WATCH_CLIENTS_HOST:-./install/clients}:/data/clients
- client-watch-state:/var/lib/client-watch
healthcheck:
test: ["CMD", "curl", "-fsS", "-o", "/dev/null", "http://127.0.0.1:8094/healthz"]
interval: 20s
timeout: 3s
retries: 3
start_period: 5s
volumes:
client-watch-state:
networks:
default:
name: none
external: true