eriol

Telegram bot to post messages from a Telegram group to Mastodon.

Go to file

Daniele Tricoli 5b074691c4 continuous-integration/drone/push Build is passing Details Update README with deploy info		2022-03-11 20:15:50 +01:00
cmd	Don't use a regexp in splitTextAtChunk	2022-03-09 03:13:00 +01:00
.dockerignore	Add dockerignore	2022-03-11 20:15:39 +01:00
.drone.yml	Test sub packages	2022-02-28 23:26:05 +01:00
.gitignore	Ignore the compiled bot	2022-03-11 16:25:03 +01:00
Dockerfile	Upgrade all the packages on the final stage	2022-03-11 19:10:21 +01:00
LICENSE	Initial import	2022-02-27 02:00:26 +01:00
README.md	Update README with deploy info	2022-03-11 20:15:50 +01:00
docker-compose.yml	Add a docker-compose file	2022-03-11 20:15:26 +01:00
go.mod	Rename the project to telegram-group2mastodon	2022-03-05 03:51:35 +01:00
go.sum	Switch to github.com/cking/go-mastodon	2022-03-01 00:50:36 +01:00
main.go	Rename the project to telegram-group2mastodon	2022-03-05 03:51:35 +01:00

README.md

telegram-group2mastodon

telegram-group2mastodon is a Telegram bot to post messages from a Telegram group to Mastodon. It's written in Go and it is relased under the AGPL3+. Since the bot must be able to read all the messages you should use it only on public groups.

Installation

Build the bot (for example if version is v0.1.0 and you are on a unix system):
```
cd /tmp; GOPATH=/tmp/go go install noa.mornie.org/eriol/telegram-group2mastodon@v0.1.0
```
You will find the binary at /tmp/go/bin/telegram-group2mastodon. You don't need to set GOPATH if you already have it set and you are fine having the bot installed there.
Create your bot using Telegram @BotFather.

The bot uses environment variables as configuration, you have to export the following (except variables with a default) before starting it:

Variable	Meaning	Default
`MASTODON_ACCESS_TOKEN`	Mastodon access token	N/A
`MASTODON_SERVER_ADDRESS`	Mastodon server address	N/A
`MASTODON_TOOT_MAX_CHARACTERS`	Toot max lenght	500
`MASTODON_TOOT_VISIBILITY`	Default toot visibility	unlisted
`TELEGRAM_BOT_TOKEN`	Telegram bot token	N/A
`TELEGRAM_CHAT_ID`	Telegram alolowed chat id	N/A
`TELEGRAM_DEBUG`	Debug messages from Telegram	False

MASTODON_TOOT_VISIBILITY allowed values are: direct, private, public and unlisted. To get MASTODON_ACCESS_TOKEN see next point.

To get MASTODON_ACCESS_TOKEN use the subcommand authenticate:
```
telegram-group2mastodon authenticate
```
and follow the istructions.
Launch the bot:
```
telegram-group2mastodon run
```

Deploy using Docker/Podman

Images are automatically built after each push on quay.io, here the list of available tags: https://quay.io/repository/eriol/telegram-group2mastodon?tab=tags

docker

Suppose you want to use the latest tag.

docker run \
    --env MASTODON_ACCESS_TOKEN=$MASTODON_ACCESS_TOKEN \
    --env MASTODON_SERVER_ADDRESS=$MASTODON_SERVER_ADDRESS \
    --env TELEGRAM_BOT_TOKEN=$TELEGRAM_BOT_TOKEN \
    --env TELEGRAM_CHAT_ID=$TELEGRAM_CHAT_ID \
    quay.io/eriol/telegram-group2mastodon:latest

podman

Suppose you want to use the latest tag.

podman run \
    --env MASTODON_ACCESS_TOKEN=$MASTODON_ACCESS_TOKEN \
    --env MASTODON_SERVER_ADDRESS=$MASTODON_SERVER_ADDRESS \
    --env TELEGRAM_BOT_TOKEN=$TELEGRAM_BOT_TOKEN \
    --env TELEGRAM_CHAT_ID=$TELEGRAM_CHAT_ID \
    quay.io/eriol/telegram-group2mastodon:latest

docker-compose

---
version: "3.9"

services:
  bot:
    image: quay.io/eriol/telegram-group2mastodon:latest
    environment:
      - MASTODON_ACCESS_TOKEN=${MASTODON_ACCESS_TOKEN}
      - MASTODON_SERVER_ADDRESS=${MASTODON_SERVER_ADDRESS}
      - TELEGRAM_BOT_TOKEN=${TELEGRAM_BOT_TOKEN}
      - TELEGRAM_CHAT_ID=${TELEGRAM_CHAT_ID}