fix: telegram bot - hacking it until it runs

This commit is contained in:
decentral1se
2022-05-12 22:27:12 +02:00
parent 467a35e7b9
commit dd4841dbe0
5 changed files with 47 additions and 12 deletions

View File

@ -2,8 +2,17 @@
version: "3.8"
services:
telegram-bridge:
app:
environment:
- TELEGRAM_APP_SERVICE_ENABLED=1
- TELEGRAM_APP_SERVICE_CONFIG=/telegram-data/registration.yaml
volumes:
- telegram-data:/telegram-data
telegram_bridge:
image: dock.mau.dev/mautrix/telegram:1f5b91cbec7866663d8dd8f4c9a62115e2905552-amd64
depends_on:
- telegram_db
configs:
- source: telegram_bridge_yaml
target: /data/config.yaml
@ -18,12 +27,16 @@ services:
- TELEGRAM_APP_ID
secrets:
- telegram_api_hash
- telegram_as_token
- telegram_bot_token
- telegram_db_password
- telegram_hs_token
volumes:
- telegram-data:/data
networks:
- internal
telegram-db:
telegram_db:
image: postgres:13-alpine
secrets:
- telegram_db_password
@ -44,7 +57,7 @@ services:
configs:
telegram_bridge_yaml:
name: ${STACK_NAME}_telegram_bridge_yaml_${TELEGRAM_BRIDGE_YAML_VERSION}
file: telegram-bridge.yaml.tmpl
file: telegram_bridge.yaml.tmpl
template_driver: golang
volumes:
@ -61,3 +74,9 @@ secrets:
telegram_bot_token:
external: true
name: ${STACK_NAME}_telegram_bot_token_${SECRET_TELEGRAM_BOT_TOKEN_VERSION}
telegram_as_token:
external: true
name: ${STACK_NAME}_telegram_as_token_${SECRET_TELEGRAM_AS_TOKEN_VERSION}
telegram_hs_token:
external: true
name: ${STACK_NAME}_telegram_hs_token_${SECRET_TELEGRAM_HS_TOKEN_VERSION}