// the take
A full commerce-grade LMS built on Phalcon (the C-extension PHP framework) for running a paid online course business — courses, chapters, video lessons, orders, refunds, VIP subscriptions, and both Alipay/WeChat payment flows, with separate admin, API, and home-facing modules. It's aimed at someone in the Chinese market who wants to stand up a koogua.com-style course platform rather than at Western devs looking for a generic LMS.
Genuinely end-to-end: order creation, trade status history, refund workflows, and VIP revocation are all implemented, not stubbed — this is a real commerce system, not a course-listing demo. The app layer separates Builders (query construction) and Caches (one class per cached entity, e.g. IndexFeaturedCourseList, MaxCourseId) from Services, which keeps the controllers thin and the caching strategy explicit instead of scattered. Current dependency versions (PHP 8.4, MySQL 8.4, Redis 8.2, Phalcon 5.20) show it's actively maintained, not frozen on an old PHP7 stack like a lot of Phalcon projects from this era. A SECURITY.md and CHANGELOG.md exist, which is more process discipline than most solo-maintainer PHP repos bother with.
Everything — README, docs links, admin UI strings — is Chinese-only, and the 'docs' links all point to the same wiki page, so there's no real setup guide for an outsider. Video delivery, transcoding, and likely SMS/storage are hard-wired to Tencent Cloud VOD, and payments are Alipay/WeChat-only; there's no abstraction layer, so deploying this outside China means rewriting a chunk of the Services layer, not just swapping a config value. Full-text search runs on xunsearch, a mostly-dormant project with its last meaningful activity years ago — betting production search on it over Elasticsearch or Meilisearch is a real operational risk. No tests directory anywhere in the tree, and Phalcon itself is a compiled C extension, which means every deploy target needs the right extension built and matched to the PHP version, an ops tax most PHP shops don't want.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →