From bf3db9999f09c15620e0e00b92b9276b7bdf64c8 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Sun, 15 May 2022 10:47:52 +0200 Subject: [PATCH] documenting the chaos --- README.md | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c6e216b..a05bc4f 100644 --- a/README.md +++ b/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 telegram_api_hash v1 +abra app secret insert telegram_bot_token v1 abra app secret generate -a + abra app deploy abra app run matrix.fva.wtf telegram_bridge cat /data/registration.yaml abra app undeploy + +abra app secret rm telegram_as_token abra app secret insert telegram_as_token v1 + +abra app secret rm telegram_as_token abra app secret insert telegram_hs_token v1 + abra app deploy ```