chore: подготовка инфраструктуры
This commit is contained in:
1 parent
a3f588c9d9
commit
76679d99f4
3 files changed
+41
-17
No files matched your search
@@ -5,3 +5,4 @@ src/db.sqlite3
|
|||||||
src/design/static_root/
|
src/design/static_root/
|
||||||
__pycache__/
|
__pycache__/
|
||||||
wheels/
|
wheels/
|
||||||
|
.env
|
||||||
+27
-17
@@ -2,12 +2,11 @@ services:
|
|||||||
xui:
|
xui:
|
||||||
# 3x-ui для тестирования api. Панель: http://127.0.0.1:2053 (по умолчанию admin/admin)
|
# 3x-ui для тестирования api. Панель: http://127.0.0.1:2053 (по умолчанию admin/admin)
|
||||||
image: docker.local/ghcr.io/mhsanaei/3x-ui:latest
|
image: docker.local/ghcr.io/mhsanaei/3x-ui:latest
|
||||||
restart: unless-stopped
|
|
||||||
environment:
|
environment:
|
||||||
XRAY_VMESS_AEAD_FORCED: "false"
|
XRAY_VMESS_AEAD_FORCED: "false"
|
||||||
XUI_ENABLE_FAIL2BAN: "false"
|
XUI_ENABLE_FAIL2BAN: "false"
|
||||||
ports:
|
ports:
|
||||||
- "2053:2053"
|
- "127.0.0.1:2053:2053"
|
||||||
volumes:
|
volumes:
|
||||||
- ./docker-services-data/xui/db/:/etc/x-ui/
|
- ./docker-services-data/xui/db/:/etc/x-ui/
|
||||||
- ./docker-services-data/xui/cert/:/root/cert/
|
- ./docker-services-data/xui/cert/:/root/cert/
|
||||||
@@ -15,39 +14,50 @@ services:
|
|||||||
telegram:
|
telegram:
|
||||||
image: docker.local/aiogram/telegram-bot-api:10.3
|
image: docker.local/aiogram/telegram-bot-api:10.3
|
||||||
environment:
|
environment:
|
||||||
TELEGRAM_API_ID: "<api-id>"
|
TELEGRAM_API_ID: $TG_APP_ID
|
||||||
TELEGRAM_API_HASH: "<api-hash>"
|
TELEGRAM_API_HASH: $TG_APP_HASH
|
||||||
volumes:
|
volumes:
|
||||||
- telegram-bot-api-data:/var/lib/telegram-bot-api
|
- telegram-bot-api-data:/var/lib/telegram-bot-api
|
||||||
ports:
|
ports:
|
||||||
- "8081:8081"
|
- "127.0.0.1:8081:8081"
|
||||||
|
- "127.0.0.1:8082:8082"
|
||||||
|
|
||||||
redis:
|
redis:
|
||||||
image: redis:latest
|
image: docker.local/redis:8.8.3-alpine
|
||||||
container_name: shop-redis
|
|
||||||
ports:
|
ports:
|
||||||
- "6379:6379"
|
- "127.0.0.1:6379:6379"
|
||||||
volumes:
|
volumes:
|
||||||
- redis_data:/data
|
- redis_data:/data
|
||||||
|
|
||||||
rabbitmq:
|
rabbitmq:
|
||||||
image: rabbitmq:latest
|
image: docker.local/rabbitmq:4.3.6-management-alpine
|
||||||
container_name: shop-rabbitmq
|
# Данные лежат в mnesia/rabbit@<hostname>, поэтому hostname и cookie фиксируем,
|
||||||
|
# чтобы при переносе volume новый контейнер смог их прочитать
|
||||||
|
hostname: $RABBITMQ_HOST
|
||||||
|
environment:
|
||||||
|
RABBITMQ_NODENAME: rabbit@$RABBITMQ_HOST
|
||||||
|
RABBITMQ_ERLANG_COOKIE: $RABBITMQ_ERLANG_COOKIE
|
||||||
|
RABBITMQ_DEFAULT_VHOST: $RABBITMQ_VHOST
|
||||||
ports:
|
ports:
|
||||||
- "5672:5672"
|
- "127.0.0.1:5672:5672"
|
||||||
- "15672:15672"
|
- "127.0.0.1:15672:15672"
|
||||||
|
volumes:
|
||||||
|
- rabbitmq_data:/var/lib/rabbitmq
|
||||||
|
|
||||||
postgres:
|
postgres:
|
||||||
image: postgres:latest
|
image: docker.local/postgres:16.15-alpine3.23
|
||||||
container_name: shop-postgres
|
container_name: shop-postgres
|
||||||
environment:
|
environment:
|
||||||
POSTGRES_DB: shop
|
POSTGRES_DB: $DB_NAME
|
||||||
POSTGRES_USER: shop
|
POSTGRES_USER: $DB_USER
|
||||||
POSTGRES_PASSWORD: shop
|
POSTGRES_PASSWORD: $DB_PASSWD
|
||||||
ports:
|
ports:
|
||||||
- "5432:5432"
|
- "127.0.0.1:5432:5432"
|
||||||
volumes:
|
volumes:
|
||||||
- postgres_data:/var/lib/postgresql/data
|
- postgres_data:/var/lib/postgresql/data
|
||||||
|
|
||||||
volumes:
|
volumes:
|
||||||
telegram-bot-api-data:
|
telegram-bot-api-data:
|
||||||
|
redis_data:
|
||||||
|
rabbitmq_data:
|
||||||
|
postgres_data:
|
||||||
+13
@@ -0,0 +1,13 @@
|
|||||||
|
# Telegram Bot API server (https://my.telegram.org/apps)
|
||||||
|
TG_APP_ID=
|
||||||
|
TG_APP_HASH=
|
||||||
|
|
||||||
|
# PostgreSQL
|
||||||
|
DB_NAME=
|
||||||
|
DB_USER=
|
||||||
|
DB_PASSWD=
|
||||||
|
|
||||||
|
# RabbitMQ: HOST и ERLANG_COOKIE не менять после первого запуска, иначе данные не прочитаются
|
||||||
|
RABBITMQ_HOST=rabbitmq
|
||||||
|
RABBITMQ_ERLANG_COOKIE=
|
||||||
|
RABBITMQ_VHOST=/
|
||||||
Reference in new issue
Block a user