Self-hosted service
PlayEdu/PlayEdu avatar
PlayEdu/PlayEdu

PlayEdu: a Gitee clone, published default credentials, and a demo mode that orphans files

A 100% open-source corporate training system with a clean UI and simple operation; deploy your own private training platform in one click.

3,325 stars576 forksJavaApache-2.0

At a glance

What is it?
PlayEdu is a Chinese enterprise training platform built on Java and MySQL, with a React 18 front end, a Spring Boot 3 back end, and a docker compose stack that starts four services on four ports. Its README is written in Chinese and short, so the real configuration reference is the env example file, which is where the warnings about JWT keys and demo mode actually live.
Who is it for?
PlayEdu suits an organisation that wants a private training portal for video courses and is prepared to read Chinese to configure it, since the feature list for the open-source edition is small and the operational detail lives in the env example rather than the README. Three things to check before it goes anywhere real.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 34 days ago.
What is it written in?
Mainly Java, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • PlayEdu/PlayEdu3,325 ★ · +31
Star history
Repository2026-09-242026-11-15
PlayEdu/PlayEdu3.3k3.3k

31 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The quick start clones from Gitee and uses the old hyphenated compose command

The installation is two commands, and both are worth reading closely. The clone URL is not GitHub:

bash
git clone --branch main https://gitee.com/playeduxyz/playedu.git playedu

So the canonical copy the instructions point at lives on Gitee under a playeduxyz account, on a branch called main, while this repository is the GitHub one. Anyone building from one and comparing against the other is comparing two trees that need not match.

The second command starts everything:

bash
cd playedu && docker-compose up -d

That is the Compose v1 spelling with a hyphen, while the compose file in the repository is named compose.yml and the current tooling is invoked as a subcommand. The file name itself is one Docker Compose looks for by default, so the mismatch is in the binary form rather than in the filename.

Four ports come up: the admin interface on 9900, the PC front end on 9800, the H5 front end on 9801 and the API on 9700. The README tells you to open the admin interface and log in with `[email protected]` and the password `playedu`.

The same default secret appears in the README, the env example and the compose file

Three published defaults have to change together, and none of them is marked as a development-only value in a way you can see from the outside.

The database password is the clearest case. The compose file gives the application a `DB_USER` defaulting to root and a `DB_PASS` defaulting to `playeduxyz`, and it uses the same value as `MYSQL_ROOT_PASSWORD` for the database container it builds from `docker/mysql`. So the application connects as the MySQL root user by default, using a password that is written into a file in the repository.

The signing key is the second. It appears as the JWT secret in the compose file and as `PLAYEDU_JWT_KEY` in the env example, and the env example is the one place the risk is stated in words: the comment says it must be changed in a production environment.

The third is the admin account itself, published in the README. Two other settings in the same file are worth knowing as defaults rather than secrets. `PLAYEDU_SA_TOKEN_IS_CONCURRENT` defaults to false, which allows the same account to be signed in from more than one place. `PLAYEDU_TZ` defaults to Asia/Shanghai and is applied to both the application and the database container.

Demo mode deletes database rows and leaves the stored files behind

The env example documents a switch whose failure mode is worse than its name suggests. `PLAYEDU_DEMO_MODE` defaults to false, and the comment above it explains what true does: when a resource is deleted, only the database record is removed and the file in object storage is not. The stated purpose is the public demo site, where an operator needs to be able to reset content without destroying what the demo depends on.

The same comment states the consequence for everyone else: keep it false in production, because the alternative leaves behind orphaned objects that can never be reclaimed. That is an accurate description of a soft delete with no garbage collector, and it is the kind of setting that is safe by default and expensive by accident.

The object storage reference in that comment also tells you something about the architecture. Video files are held in S3-compatible storage rather than on a local volume, which matches the open-source edition's advertised feature of private video storage. The compose file persists only one named volume, the MySQL data directory. So media is external to the stack by design, and where it lives is a deployment decision this repository does not make for you.

Apache-2.0 in the license file, and four usage notes that say something different

The license recorded for this repository is Apache-2.0, and a LICENSE file sits at the root. The README then adds four numbered notes about use, and they are not neutral.

Copyright is assigned to Hangzhou Baishu Technology, which the file describes as holding complete copyright of the open-source version with all usage rights reserved. Modification is permitted only under the open source terms, and every change must be recorded as an explicit note in the code describing what was changed. Deleting, altering or tampering with the copyright information or the open-source description files in the source is prohibited, with legal action named as the consequence. And in any use scenario the original copyright information must be preserved, including the Designed By PlayEdu page mark, the links to the official site, and the open-source notes in the code.

So the terms in the README impose obligations that a plain Apache-2.0 grant does not state: a mandatory page attribution and links that survive in any deployment. Both readings can be true at once, because Apache-2.0 lets a distributor add its own conditions to its own contribution. Which applies to your use, and whether keeping a vendor mark in your internal portal is acceptable to you, is a question for whoever owns that decision rather than for the license file.

The image builds three front ends and a five-module jar, and skips the tests on the way

The Dockerfile is the clearest description of what this software is. A Node stage on an Alpine base installs dependencies for the admin, PC and H5 front ends with pnpm, using each one's lock file, and builds all three with `VITE_APP_URL=/api/` set so the bundles call the API through a relative path. A second stage on a Temurin base copies the Maven wrapper and the poms for five modules, playedu-api, playedu-common, playedu-course, playedu-resource and playedu-system, then fetches dependencies offline and packages the jar while skipping tests entirely:

dockerfile
RUN /app/mvnw -B -DskipTests dependency:go-offline
RUN /app/mvnw -B -Dmaven.test.skip=true package

The runtime stage copies the jar, the three built front end directories, and an nginx configuration from the docker directory, then exposes the four service ports.

Two details have consequences outside the build. The base images are pulled from a namespaced registry rather than from a public default, which means your build depends on that namespace remaining reachable from wherever you build. And skipping tests in the image build means a passing deployment tells you nothing about the test suite, so run it separately if you care.

The open-source edition is five features; everything else is the commercial product

The README is written in Chinese, and that is where the scope is defined. The open-source edition is described as providing department management, learner management, online video learning, learner progress tracking and private video storage. That is the whole list.

Everything else in the file belongs to the enterprise edition: audio and video learning, online document preview, online exams and learning tasks, plus security measures described as video transcoding encryption, anti-leeching protection, prevention of fast-forwarding, and prevention of idling. It also names integrations with WeCom, DingTalk and Feishu. The header of the README links separately to the commercial edition page, to a deployment handbook on the project's FAQ site, and to a public demo of the open-source edition, and it opens with a sponsored link for an unrelated domain certificate service.

For an evaluator, the useful reading is that the open-source repository is the video-course skeleton: content, people, progress. Exams, tasks and document handling are the paid tier. The repository also carries a changelog file, and the newest tagged release is 2.2 from May 2026, with the default branch pushed on 19 May 2026.

Editorial conclusion

PlayEdu suits an organisation that wants a private training portal for video courses and is prepared to read Chinese to configure it, since the feature list for the open-source edition is small and the operational detail lives in the env example rather than the README. Three things to check before it goes anywhere real. Change the JWT signing key, because the default ships in both the env example and the compose file, and change the database root password for the same reason. Leave demo mode off, because it deletes database records without deleting the stored objects and leaves files nobody can reclaim. And settle the licensing question with whoever owns the trademark for you, because the license file and the usage notes in the README do not say quite the same thing, and the notes carry legal consequences of their own.

Frequently asked questions

How do I start a PlayEdu instance?

Clone the repository with git clone --branch main https://gitee.com/playeduxyz/playedu.git playedu, then run cd playedu && docker-compose up -d, then open http://localhost:9900 for the admin interface.

What are the default PlayEdu ports and admin credentials?

The admin interface is on port 9900, the PC front end on 9800, the H5 front end on 9801 and the API on 9700. The README gives the default admin account as [email protected] with the password playedu.

What should be changed before running PlayEdu in production?

The env example says the JWT signing key must be changed in production, and that PLAYEDU_DEMO_MODE must stay false, because demo mode deletes only database records and leaves unreclaimable objects in storage.

What license is PlayEdu released under?

Apache-2.0 is recorded for the repository, while the usage notes in the README state that Hangzhou Baishu Technology holds complete copyright of the open-source version, that every modification must be documented in the code, and that copyright marks such as Designed By PlayEdu and the official site links may not be removed.

Which database does PlayEdu use?

MySQL, with a Hikari connection pool. The compose file builds a mysql service from the docker directory, defaults the database name to playedu and the root password to playeduxyz, and publishes that container on host port 23307.

Official sources

  1. License: Apache-2.0
  2. PlayEdu/PlayEdu on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/playedu-playedu.svg)](https://hysenlabs.com/projects/playedu-playedu)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/playedu-playedu.svg)](https://hysenlabs.com/projects/playedu-playedu)

Was this useful?