YYeTsBot's Docker Stack: Four Datastores and a Frontend Fetched at Build Time

Four datastores, and the bot only waits on two of them

docker-compose.yml defines four stateful services and two application services drawn from the same image. Redis runs the redis:7-alpine image, MongoDB runs mongo:6 with a quiet command and a bind of 127.0.0.1:27017, search runs getmeili/meilisearch:v1.0.2 with MEILI_HTTP_PAYLOAD_SIZE_LIMIT set to 1073741824, and MySQL runs ubuntu/mysql:8.0-22.04_beta. The dependency asymmetry is the part worth noting. The bot service declares depends_on redis and mongo only, while the web service declares mongo, redis and mysql. So the Telegram side can come up without the search index or MySQL, and the web side cannot. Budget for four containers rather than one, and remember that the bot answering messages and the site you browse are two processes from one image, not one process.

env/yyets.env is referenced but never shipped

Both application services load their configuration from a file the repository does not contain:

    env_file:
      - env/yyets.env

There is no env directory in the tree, no example file beside it, and no enumeration of the keys it needs anywhere in the README. The consequence is immediate and unglamorous. Clone the repository, author your compose file, run it, and the containers have nothing to read. Everything a deployment needs is therefore either inferable from the code or carried over from somebody else's running instance. Treat that env file as the real configuration surface of this project, because in practice it, rather than the compose file, decides how your instance behaves.

setup.py advertises one dependency and a Python floor that no longer holds

The packaging metadata tells a different story from the real one. setup.py declares:

REQUIRES_PYTHON = ">=3.6.0"

and a REQUIRED list holding only requests, with an empty EXTRAS dictionary and a hand written VERSION constant of 1.0.1. Meanwhile requirements.txt lists twenty five lines covering pytelegrambotapi, tornado, pymongo, redis, meilisearch, playwright and more, and the Dockerfile builds on python:3.14-slim. Two consequences follow. Installing this project with pip gives you a distribution that declares one dependency and cannot run either the site or the bot, so the compose route is the only sane install. And the 3.6 floor is fiction next to those pins, so read the metadata as a leftover rather than a compatibility promise, and note that the version it reports matches neither published release.

One dependency installs from a git URL and is never pinned

Almost every line in requirements.txt carries an exact version behind an equals sign. One does not:

git+https://github.com/tgbot-collection/python-akismet

A VCS requirement resolves to whatever the branch tip is at install time, so the Akismet side can change underneath a deployment without any version of this project changing. That line also explains an otherwise puzzling detail in the Dockerfile, where git is installed into the pybuilder image before pip runs, because pip has to clone to satisfy it. If you care about reproducible builds, resolve that one dependency to a commit yourself, because the repository gives you no way to know which revision it was tested against.

The image downloads a dated frontend zip while it builds

The web interface is not built here. A separate nodebuilder stage pulls a release asset from the YYeTsFE repository:

RUN curl -fL https://github.com/tgbot-collection/YYeTsFE/releases/download/ads-2026-05-22/build.zip -o build.zip

The runner stage then copies the unzipped result straight over the templates directory. Note that the asset tag is a date, ads-2026-05-22, which pins the shipped interface to a build somebody compiled in a different repository. Two consequences follow for anyone building from source. Your build needs network access to a third party release asset, and if that asset is ever removed the stage fails with nothing but a curl error to explain it. So the application image is not reproducible from this repository alone; you also need that one zip, and you have no way to regenerate it from what is checked in here.

A root password in the compose file, loopback ports and a Shanghai clock

Several defaults suit a laptop and suit nothing else. MySQL starts with MYSQL_ROOT_PASSWORD set to the literal string root, and three of the four stateful services set their logging driver to none, so a failure at startup leaves you with little to read. MongoDB and the web service publish host-local bindings only, 127.0.0.1:27017 and 127.0.0.1:8888 plus 172.17.0.1:8888, which means nothing is reachable from your network until you edit the file yourself. The image also pins a timezone:

ENV TZ=Asia/Shanghai

so anything scheduled through apscheduler runs on that clock regardless of where the host sits. One inconsistency is worth checking on your first build: tzdata is installed in the runner stage, yet the zoneinfo directory is copied from the pybuilder stage, which installs only git.

No releases since 2024, and running it moves the takedown duty to you

The two published releases were both cut on 7 January 2024, one tagged as an app version and one as an offline one click package, while the default branch took its last push on 27 July 2026. Nothing in between is versioned. A self-hosted instance is therefore whatever master produced that day, and the bot and web services use the bennythink/yyetsbot image with no tag. On top of that, the project states that it stores, uploads and distributes no video files, that comment links are posted by users, that the author is not responsible for third party content, and that infringement reports should be sent for removal. Read those as a description of the hosted service. The moment you run your own instance, the last sentence stops being about the author.

Editorial conclusion

YYeTsBot is worth reading if you want to see how a small Python team stitched a Telegram bot, a Tornado site and four datastores into one compose file, and it is worth running only if you are prepared to own the parts the project leaves open: an env file nobody documents, a root password written into the compose file, a build that depends on a frontend release asset, and the takedown duty for links your own users post. Pin an image tag and change the credentials before it faces any network.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. Releases
5. tgbot-collection/YYeTsBot on GitHub