fix: telegram bot - hacking it until it runs
This commit is contained in:
13
README.md
13
README.md
@ -82,5 +82,18 @@ This could be implemented in this recipe but we haven't merged it in yet. Change
|
||||
|
||||
### Telegram bridging
|
||||
|
||||
> WIP
|
||||
|
||||
Setting it up is a bit of a chicken/egg & chasing cats moment. Here is a rough guide:
|
||||
|
||||
- `abra app secret generate -a <domain>` (generates invalid secret values)
|
||||
- `abra app deploy <domain>`
|
||||
- `abra app run matrix.fva.wtf telegram-bridge cat /data/registration.yaml` (get your app service secrets)
|
||||
- `abra app undeploy <domain>`
|
||||
- `abra app secret insert <domain> telegram_as_token v1 <secret>`
|
||||
- `abra app secret insert <domain> telegram_hs_token v1 <secret>`
|
||||
- `abra app deploy <domain>`
|
||||
- ??? api/hash/token ???
|
||||
|
||||
- [`docs.mau.fi`](https://docs.mau.fi/bridges/python/setup/docker.html?bridge=telegram)
|
||||
- [`example-config.yaml`](https://mau.dev/mautrix/telegram/-/blob/master/mautrix_telegram/example-config.yaml)
|
||||
|
Reference in New Issue
Block a user