documenting the chaos
This commit is contained in:
parent
00b0375b1c
commit
bf3db9999f
20
README.md
20
README.md
|
@ -84,15 +84,33 @@ This could be implemented in this recipe but we haven't merged it in yet. Change
|
|||
|
||||
> WIP
|
||||
|
||||
Setting it up is a bit of a chicken/egg & chasing cats moment. Here is a rough guide:
|
||||
Setting it up is a bit of a chicken/egg & chasing cats moment.
|
||||
|
||||
You need to get your bot setup on the telegram side first and have these values:
|
||||
|
||||
```
|
||||
api_id: ...
|
||||
api_hash: ...
|
||||
telegram_bot_token: ...
|
||||
```
|
||||
|
||||
Here is a rough guide:
|
||||
|
||||
```
|
||||
abra app secret insert <domain> telegram_api_hash v1 <secret>
|
||||
abra app secret insert <domain> telegram_bot_token v1 <secret>
|
||||
abra app secret generate -a <domain>
|
||||
|
||||
abra app deploy <domain>
|
||||
abra app run matrix.fva.wtf telegram_bridge cat /data/registration.yaml
|
||||
abra app undeploy <domain>
|
||||
|
||||
abra app secret rm <domain> telegram_as_token
|
||||
abra app secret insert <domain> telegram_as_token v1 <secret>
|
||||
|
||||
abra app secret rm <domain> telegram_as_token
|
||||
abra app secret insert <domain> telegram_hs_token v1 <secret>
|
||||
|
||||
abra app deploy <domain>
|
||||
```
|
||||
|
||||
|
|
Loading…
Reference in New Issue