JooLun-wx is a WeChat mall built on the RuoYi admin scaffold

A RuoYi-Vue fork with a shop bolted on

The lineage decides most of what this project is. The README states that the project is a secondary development of RuoYi-Vue with MybatisPlus, Avue and the WxJava SDK integrated, and that it is a professional WeChat management framework with a mini program mall added. So the admin half of the system, the users, departments, posts, menus, roles, dictionaries, parameters, notices, operation and login logs, online users, scheduled jobs, service and cache monitoring, is the familiar RuoYi module set, and the shop half, the data dashboard, the home page decoration, mall customers, after-sales management, product categories, product management, order management, the mini program customers, the shopping cart, shipping addresses, mini program user management and the official account modules for tags, users, messages, assets, custom menus, automatic replies and marketing statistics, is the added layer. The stack is stated in the badges as Java 21 and Spring Boot 4.1.1, and the platform description names Spring Boot 4, Spring Security, Redis with JWT, MybatisPlus and WxJava on the back end, Vue 3, Element Plus and Avue 3 on the admin front end, and a native mini program front end with Color UI. The repository itself is split into three directories matching that split: joolun-wx for the Java backend, joolun-wx-ui for the admin pages and joolun-wx-ma for the mini program shop front end.

The code generator is the reason to pick this over plain RuoYi

Two features in the built-in function list decide whether this fork saves you time or just adds weight. The first is code generation, described as generating front end and back end code for java, html, xml and sql with CRUD download support. The second is a system interface feature that automatically generates API documentation for the business code. The generator is what turns the fork from a pile of copied modules into a starting point for your own domain, because you draw the tables and get the entity, mapper, service, controller and the matching pages. Alongside it is an online builder for dragging form elements to generate HTML, and a code analysis note about the connection pool monitor being able to analyse SQL to find performance bottlenecks, which is a hint that the operational tooling is RuoYi's rather than something new. The permissions model is the other thing inherited worth naming. Authentication uses JWT and supports a multi terminal authentication system, with dynamically loaded permission menus and several ways of controlling permissions, and the role module assigns menu permissions, sets button permission identifiers, and configures data scope permissions per organisation.

Deploying with one script, and what the installer does for you

The repository offers a Docker Compose distribution aimed at ordinary users rather than operators, and the point of it is that the target server needs no Java, Maven, Node.js, MySQL, Redis or Nginx installed. Using the distribution package, the only command to run is this.

./install.sh

The README explains what happens next: the installer automatically generates the keys, initialises the database, sets a random temporary administrator password and waits for the services to become healthy. That last detail is the one that matters for a first run, because it means the credential you need is not the one you would have chosen, and the password is temporary. The system requirements for the classic route are listed separately and are modest: JDK 21, MySQL 8 and Maven 3.0 or newer. The repository also links to server deployment and local run documentation on the project's wiki, and a jar based deployment guide for teams who already have a Java environment, so the Compose route is an option rather than the only route. The management backend has a public demo at demo2.joolun.com, which is worth opening before you install anything, since the demo shows the assembled admin interface with the shop and official account modules populated.

The open source edition stops at single tenant, single mall

This is the constraint to understand before you plan the project, and the README states it in a comparison table between editions. The open source edition runs on a RuoYi Spring Boot single application, with simple functionality, a single tenant, a single mall, a single official account and a single mini program, and the only terminal it includes is the mini program. The comparison table contrasts it with a paid edition built on a microservices stack with a separated Vue front end and uniapp, richer marketing tooling, custom drag and drop shop decoration, service provider payments, several object storage options, multi tenant, multi store, and a much wider set of terminals. So the features people usually associate with a modern Chinese mall suite, multi tenant, multiple storefronts and extra clients, are not in the MIT repository. If your requirement is one shop for one official account, the open source edition is sufficient. If it is a platform for many merchants, you are reading a different product's documentation.

Two support caveats the README puts in writing

Two disclaimers sit in the platform section and both matter for planning. The first is that the open source edition provides no manual service, and that problems or bugs should be filed as issues on Gitee, where the team says they will be handled periodically. The second is the licensing of responsibility itself: the README asks you to test against your own business requirements before using it, and states that JooLun is not responsible for any loss caused by framework problems. That is a normal position for a free framework, but it interacts with the fact that this code will be running payments and orders. There is also a hosting detail that changes where you file things. The README says the project is hosted in real time on Gitee and that the main branch should be used directly, and issues should be raised on Gitee. The GitHub repository you are reading is therefore a mirror for discovery, and a bug you file on GitHub may not reach the people who can fix it. The development documentation lives on a separate wiki at wiki.joolun.com, so the wiki rather than the repository is where the setup detail lives.

A maintenance line that ships often

The project is not archived and the last push was on 2026-10-12, the same day as the newest release. The two most recent releases are 3.9.2 on 2026-10-12 and 3.9.1 on 2026-09-16, so the versioning is a single 3.9 line moving forward, which is the pattern of a project that versions the whole stack together rather than its modules independently. The licence is MIT, with the licence file at the root of the repository, so commercial use and modification carry no copyleft obligation, though your own review should cover the third party components pulled in through RuoYi, Avue, MybatisPlus and WxJava, which have their own terms. The upgrade question for an adopter is a practical one. Because the project advertises full support for the Spring Boot 4 ecosystem, a JooLun-wx upgrade is also a Spring Boot and MybatisPlus upgrade, and the dependency tree underneath a RuoYi-derived project is deep. Pinning a version, testing the payment and order paths after each bump, and keeping your own business logic outside the generated code are the three habits that pay off here. The version numbers in the badges and the release tags are the ones to compare against, since the framework versions move independently of the project version.

Editorial conclusion

JooLun-wx suits a Java team that has to ship a WeChat mini program shop and would rather start from a working RuoYi-Vue fork with the mall features, the official account tooling and the code generator already in place than write them. It is the wrong tool if you need multi-tenant, multiple stores, an H5 or app client, or a microservices deployment, because the comparison table in the README puts all of that in the paid edition, and it is the wrong tool if you need commercial support, since the open source edition explicitly offers no manual service. Before you build on it, run the Docker Compose install on a scratch machine, since the installer generates keys, initialises the database and sets a random administrator password, then read the issue tracker on Gitee rather than GitHub, because the project is maintained there.

Frequently asked questions

Official sources

1. Joolun/JooLun-wx on GitHub
2. License: MIT
3. Project website
4. README
5. Releases