https://github.com/aiogram/telegram-bot-api

Docker image of Telegram Bot API Server

https://github.com/aiogram/telegram-bot-api

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (11.2%) to scientific vocabulary

Keywords from Contributors

aiogram asyncio bot-framework telegram-bot telegram-bot-api
Last synced: 11 months ago · JSON representation

Repository

Docker image of Telegram Bot API Server

Basic Info
Statistics
  • Stars: 232
  • Watchers: 8
  • Forks: 65
  • Open Issues: 3
  • Releases: 0
Created over 5 years ago · Last pushed over 1 year ago
Metadata Files
Readme

README.md

Unofficial Docker image of Telegram Bot API

Here is Docker image for https://github.com/tdlib/telegram-bot-api

The Telegram Bot API provides an HTTP API for creating Telegram Bots.

If you've got any questions about bots or would like to report an issue with your bot, kindly contact us at @BotSupport in Telegram.

Quick reference

Before start, you will need to obtain api-id and api-hash as described in https://core.telegram.org/api/obtainingapiid and specify them using the TELEGRAM_API_ID and TELEGRAM_API_HASH environment variables.

And then to start the Telegram Bot API all you need to do is docker run -d -p 8081:8081 --name=telegram-bot-api --restart=always -v telegram-bot-api-data:/var/lib/telegram-bot-api -e TELEGRAM_API_ID=<api_id> -e TELEGRAM_API_HASH=<api-hash> aiogram/telegram-bot-api:latest

Configuration

Container can be configured via environment variables

TELEGRAM_API_ID, TELEGRAM_API_HASH

Application identifiers for Telegram API access, which can be obtained at https://my.telegram.org as described in https://core.telegram.org/api/obtainingapiid

TELEGRAM_STAT

Enable statistics HTTP endpoint.

Usage: -e TELEGRAM_STAT=1 -p 8082:8082 and then check that curl http://<host>:8082 returns server statistic

TELEGRAM_FILTER

"/". Allow only bots with 'botuserid % modulo == remainder'

TELEGRAM_MAX_WEBHOOK_CONNECTIONS

default value of the maximum webhook connections per bot

TELEGRAM_VERBOSITY

log verbosity level

TELEGRAM_LOG_FILE

Filename where logs will be redirected (By default logs will be written to stdout/stderr streams)

TELEGRAM_MAX_CONNECTIONS

maximum number of open file descriptors

TELEGRAM_PROXY

HTTP proxy server for outgoing webhook requests in the format http://host:port

TELEGRAM_LOCAL

allow the Bot API server to serve local requests

TELEGRAM_HTTP_IP_ADDRESS

Use the TELEGRAM_HTTP_IP_ADDRESS: "[::]" parameter to listen on the ipv6 intranet

TELEGRAM_HTTP_PORT

Set which port the api server should listen to if you want to run the image in network mode as host and want to change the port.

If not set then the api server will listen to port 8081.

Start with persistent storage

Server working directory is /var/lib/telegram-bot-api so if you want to persist the server data you can mount this folder as volume:

-v telegram-bot-api-data:/etc/telegram/bot/api

Note that all files in this directory will be owned by user telegram-bot-api and group telegram-bot-api (uid: 101, gid: 101, compatible with nginx image)

Usage via docker stack deploy or docker-compose

```yaml version: '3.7'

services: telegram-bot-api: image: aiogram/telegram-bot-api:latest environment: TELEGRAMAPIID: "" TELEGRAMAPIHASH: "" volumes: - telegram-bot-api-data:/var/lib/telegram-bot-api ports: - "8081:8081"

volumes: telegram-bot-api-data: ```

Owner

  • Name: aiogram
  • Login: aiogram
  • Kind: organization
  • Email: github@aiogram.dev

GitHub Events

Total
  • Issues event: 7
  • Watch event: 63
  • Delete event: 1
  • Issue comment event: 6
  • Push event: 18
  • Pull request event: 8
  • Fork event: 15
  • Create event: 1
Last Year
  • Issues event: 7
  • Watch event: 63
  • Delete event: 1
  • Issue comment event: 6
  • Push event: 18
  • Pull request event: 8
  • Fork event: 15
  • Create event: 1

Committers

Last synced: about 1 year ago

All Time
  • Total Commits: 71
  • Total Committers: 9
  • Avg Commits per committer: 7.889
  • Development Distribution Score (DDS): 0.239
Past Year
  • Commits: 28
  • Committers: 5
  • Avg Commits per committer: 5.6
  • Development Distribution Score (DDS): 0.357
Top Committers
Name Email Commits
JRoot Junior j****r@g****m 54
jieggii j****i@p****m 5
Oleg A t****r@m****u 4
kiki-kanri a****6@g****m 2
Danipulok d****k@g****m 2
𝓥𝓐𝓘 | | 𝓟𝓻𝓸𝓰𝓻𝓪𝓶𝓶𝓮𝓻 v****o@g****m 1
youlovesaturn y****n@i****m 1
T1MOXA d****a@u****t 1
InPRTx i****x@g****m 1
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 11 months ago

All Time
  • Total issues: 14
  • Total pull requests: 17
  • Average time to close issues: 3 months
  • Average time to close pull requests: about 1 month
  • Total issue authors: 14
  • Total pull request authors: 11
  • Average comments per issue: 2.43
  • Average comments per pull request: 0.59
  • Merged pull requests: 12
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 4
  • Pull requests: 6
  • Average time to close issues: 12 days
  • Average time to close pull requests: 8 days
  • Issue authors: 4
  • Pull request authors: 3
  • Average comments per issue: 0.5
  • Average comments per pull request: 0.17
  • Merged pull requests: 3
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • Nemnon (1)
  • Olegt0rr (1)
  • ShlomiPorush (1)
  • EvgeniyKr1980 (1)
  • kiki-kanri (1)
  • TopperBG (1)
  • edbek (1)
  • jieggii (1)
  • hacker-hackman (1)
  • mercuree (1)
  • RubberArchind (1)
  • EtaoinWu (1)
  • arshiay (1)
  • goshgarmirzayev (1)
Pull Request Authors
  • kiki-kanri (4)
  • JrooTJunior (4)
  • Danipulok (3)
  • jieggii (2)
  • Vadim-Khristenko (2)
  • Olegt0rr (2)
  • InPRTx (1)
  • youlovesaturn (1)
  • mercuree (1)
  • migue802 (1)
  • T1MOXA (1)
Top Labels
Issue Labels
security (1) good first issue (1)
Pull Request Labels
enhancement (1) documentation (1)

Dependencies

.github/workflows/docker-image.yml actions
  • actions/cache v2 composite
  • actions/checkout v2 composite
  • docker/build-push-action v2 composite
  • docker/login-action v1 composite
  • docker/setup-buildx-action v1 composite
  • docker/setup-qemu-action v1 composite
Dockerfile docker
  • alpine 3.17.2 build
example/docker-compose.yml docker
  • aiogram/telegram-bot-api latest
  • nginx 1.19-alpine