Kowalski (Node.js Telegram Bot)

Kowalski is a a simple Telegram bot made in Node.js.

You can find Kowalski at @KowalskiNodeBot on Telegram.

Self-host requirements

Node.js 20 or newer (you can also use Bun)
A Telegram bot (create one at @BotFather)
FFmpeg (only for the /yt command)
Docker and Docker Compose (only required for Docker setup)

Run it yourself, develop or contribute with Kowalski

First, clone the repo with Git:

git clone https://github.com/ABOCN/TelegramBot

And now, init the submodules with these commands (this is very important):

cd TelegramBot
git submodule update --init --recursive

Next, inside the repository directory, create a config.env file with some content, which you can see the example .env file to fill info with. To see the meaning of each one, see the Functions section.

After editing the file, save all changes and run the bot with npm start.

Tip

To deal with dependencies, just run npm install or npm i at any moment to install all of them.

Running with Docker

Important

Please complete the above steps to prepare your local copy for building. You do not need to install FFmpeg on your host system.

You can also run Kowalski using Docker, which simplifies the setup process. Make sure you have Docker and Docker Compose installed.

Using Docker Compose

Make sure to setup your config.env file first!
Run the container
```
docker compose up -d
```

Note

The -d flag causes Kowalski to run in the background. If you're just playing around, you may not want to use this flag.

Using Docker Run

If you prefer to use Docker directly, you can use these instructions instead.

Make sure to setup your config.env file first!
Build the image
```
docker build -t kowalski .
```

Run the container

docker run -d --name kowalski --restart unless-stopped -v $(pwd)/config.env:/usr/src/app/config.env:ro kowalski

Note

The -d flag causes Kowalski to run in the background. If you're just playing around, you may not want to use this flag.

config.env Functions

botSource: Put the link to your bot source code.
botToken: Put your bot token that you created at @BotFather.
botAdmins: Put the ID of the people responsible for managing the bot. They can use some administrative + exclusive commands on any group.
lastKey: Last.fm API key, for use on lastfm.js functions, like see who is listening to what song and etc.
weatherKey: Weather.com API key, used for the /weather command.

Note

Take care of your config.env file, as it is so much important and needs to be secret (like your passwords), as anyone can do whatever they want to the bot with this token!

About/License

BSD-3-Clause - 2024 Lucas Gabriel (lucmsilva).

3.2 KiB Raw Blame History