This source code package is a full-stack entertainment platform built with ThinkPHP, MySQL 8, and Docker Compose, covering roughly 13 bindable template skins, a dual-channel game vendor library (FS/XH), a 10-currency interface configuration, and a Telegram bot login module — distributed on dajian168 strictly for educational research only, for developers who want to understand how multi-language settlement and agent-finance systems are structured. The front and back ends ship pre-compiled, so review value lies in configuration, data models, and deployment topology rather than editable business logic.
Key takeaway: the system separates the main site from template domains, so you can study multi-tenant routing without touching nginx manually. When I deployed this on a clean Ubuntu box, the gateway came up on port 18080, which conveniently avoids conflicts with the BT panel’s 80/443. The package pulls nginx:1.27-alpine and mysql:8.0 images online during installation — plan for that if your environment has restricted outbound access.
Three things worth examining in testing:
/ut-admin and a super-admin console at /superadmin, each with separate permission scopes and login logs.Actionable takeaway: before install, verify Docker and Docker Compose versions, then run the one-click script and confirm port 18080 is free. If the image pull fails, pre-load the two base images manually.
Key takeaway: the standalone number-data polling engine — with configurable poll cycles, external data sources, bet records, and odds tables — is the most technically interesting part of this package. In testing I found the polling interval and external source endpoints are fully configurable from the backend, which makes it a decent reference for anyone building scheduled data-ingestion jobs in ThinkPHP 6.
The finance side is equally detailed. The backend exposes:
| Module | Count / Detail | Notes for Reviewers |
|---|---|---|
| Templates | Up to 13 skins | Each binds to an independent domain |
| Currencies | 10 (CNY, USD, PHP, VND, THB, IDR, MYR, KRW, JPY, BRL) | Configured in the API settings page |
| Vendor channels | 2 (FS, XH) | Per-vendor on/off switches live in the database |
| Admin panels | 2 (/ut-admin, /superadmin) | Check permission tables for scope differences |
Judging criterion: if your goal is studying settlement or risk-control flows, trace the fund-flow and callback tables first — the pre-compiled code means the database schema is your primary documentation.
Key takeaway: 2-core/4GB is the minimum for testing; production-style review needs 4-core/8GB plus disk headroom for database growth. The Telegram integration is more than a notification hook — it covers account binding, login passphrases, verification codes, broadcast messaging, and a customer-service relay, which is a useful pattern for anyone studying bot-based auth in a communication-system category project.
nginx:1.27-alpine and mysql:8.0 load.Pitfall to avoid: since both front and back ends are compiled and unmodifiable, do not plan on refactoring business logic — budget your time for schema analysis and configuration review instead. Also note the MySQL 8 instance is bundled; you can swap to the BT panel’s MySQL, but migrate the character set settings carefully or multilingual data will garble.
Q: Can I modify the front-end templates in this source code download?
No. The front and back ends are distributed pre-compiled, so template changes are limited to the 13 built-in skins and their domain bindings. Configuration-level customization is fully supported.
Q: Does the Telegram bot login work without extra setup?
It requires binding and passphrase configuration in the backend first. The module includes login, verification-code, broadcast, and relay functions, all toggled from the super-admin panel.
Q: What is the minimum server for a full review of this platform?
2 cores and 4GB RAM for functional testing; 4 cores and 8GB is recommended when running all modules, including the data polling engine and payment callbacks, concurrently.







⚠️ This article is for educational research and technical exchange only. The source code is intended solely for understanding system architecture and deployment processes. Do not use it for illegal purposes. Any commercial operation is unrelated to the author.