# linfeng-community: a Java and Vue social forum kit with three front ends > linfeng-community is a Spring Boot forum system shipped with a Vue admin console and two uni-app user clients, one on Vue 2 and one on Vue 3. It is a large, feature-heavy reference project with a lot of surface area, and the README makes clear that the open source edition is for study and that the SQL scripts are not in the repository. **virus010101/linfeng-community** — 林风社交论坛小程序|H5论坛|App论坛|PC端圈子社区论坛系统是java+vue+uniapp开发的前后端分离社交论坛问答发帖/BBS社区论坛系统，包括论坛图文帖视频圈子聊天支付签到充值等圈子论坛小程序论坛App功能 - Repository: https://github.com/virus010101/linfeng-community - Website: https://www.linfengtech.cn - Stars: 612 · Forks: 55 - Language: Vue - License: not declared - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/virus010101-linfeng-community ## One Spring Boot backend, three separate front end code bases linfeng-community is a social forum system built as a front end and back end separated project. The backend is Java on Spring Boot, with MybatisPlus, Shiro, JWT, Redis and Websocket. The user facing side is uni-app, and the administration side is Vue. What makes the layout unusual is that the front ends are not separate repositories. The admin console lives inside the backend tree at src\main\resources\static\linfeng-community-vue. The uni-app user client for Vue 2 lives at src\main\resources\static\linfeng-community-uniapp-ky, and the newer Vue 3 client at src\main\resources\static\linfeng-community-uniapp3-ky. The README states that all three ends are published as open source for study. The user client is designed to compile to several targets from one codebase. The project description lists a mini program, an H5 web build, an App build and a PC web product, and the feature list covers the things a Chinese style community app usually needs: image and text posts, long form posts, short video, circles, private chat, WeChat Pay, paid posts, points check-in, wallet top-up, points redemption, topic tags, a prize wheel, phone and email login, a human-posting check, instant messaging, a friends module, experience levels and third party content review. The top level of the repository is small and Java shaped, with a pom.xml, a sql directory, a src directory and an images directory. ## The installation notes name the version constraints that will bite you The setup section of the README is a numbered list, and three of the items are constraints rather than steps. First, configure the database and Redis, and start Redis before starting the backend API service. The database must be MySQL 5.7 or a version above 5.7. The admin front end is built with npm install followed by npm run dev, and the node version must be less than or equal to 14. The mobile client is opened in HBuilderX, and you run npm install at the root of the uni-app project before starting it. The Node constraint of 14 or lower is the one to plan around, since the admin console predates the current Node release line and the front end has not been moved to a modern toolchain. The uni-app client is a separate install, because it is a separate project directory. Two further items are about where to get things rather than how to run them. The README says the preferred update source is the Gitee mirror, and that the related documentation and SQL files are distributed through QQ groups, with two group numbers given. The SQL files are not in the repository, so a checkout alone is not a running system. ## The SQL scripts and documentation live outside the repository This is the single most important thing to know before you plan around this project. The README states that the SQL files are open source but are distributed through the QQ group, and that the way to obtain them is to star the repository on GitHub and then join a group with your GitHub username noted. Two group numbers are listed, one of which is marked as full at 2000 members and one of which is described as a newer group that can be joined. The documentation and related files are obtained the same way, according to the installation notes. So the repository is a code drop without its database schema and without its documentation. For a learning project that is an inconvenience, since you can reconstruct a schema from the entities or ask in the group. For a production deployment it is a blocker, because you cannot build the schema, and the person who puts it in front of users needs a repeatable setup path. There is a related caveat about the demo sites. The README notes that the demo site is the standard edition, and points to a version page listing what the open source edition contains. The live demos, the H5 build, the mini program, the PC web product and the admin console demo all sit on the project domain, and the demo account is already included and can be logged into directly. ## The open source terms limit you to study and forbid resale The open source notice lists four points, and they are the constraints to read before anything else. The open source edition may only be used for personal study and research. Modifying or selling the code and resources in any form or under any name is prohibited. Commercial use is restricted, and the README says to contact the authors or consult the website for commercial terms. The software is also registered for software copyright, with two registration numbers given. There is no recognised open source licence: the repository records its licence as unknown, and the terms above are written in prose in the README rather than in a licence file. In practice this means the repository is a study artefact and a demonstration of how this kind of product is built, not a codebase you can base a commercial community on without a separate agreement. The README points to a page that contrasts the commercial and open source editions, and tells readers to consult customer service for the standard commercial edition. If your goal is to run a community platform for money, the honest reading is that you need the commercial edition, and the open source drop is the sample you evaluate first. ## The release notes read like a product changelog, not a library changelog The README carries a long version history, and the current version is V3.4.0, dated 2026.08.03. The entries are written as a commercial product's release notes, with new features, optimisations and fixes numbered in Chinese, and they show what the project actually does. The most telling recent entry is that the admin console can now generate post content by topic using deepseek, and that the human-posting check content is now generated by deepseek as well. Other recent additions include an admin panel for circle data statistics, a cover image cropper and attachment upload for admin posts, and a user bill view in the user and withdrawal modules. Looking back, V3.0.0 on 2025.12.08 moved the backend to JDK 17 and Spring Boot 3.5, upgraded the Maven dependencies and the swagger documentation version, and reorganised the DTO and VO directories. V1.25.0 on 2025.10.20 moved the user client from uni-app Vue 2 to Vue 3 and rewrote it from the Options API to the Composition API. V1.23.0 on 2025.07.11 rebuilt the websocket module and added cluster deployment support, and V1.20.0 moved websocket to a long connection mechanism with heartbeat detection. The repository is not archived and the last push was on 2026-09-29, and it publishes no GitHub releases, so the version history lives in the README and on the project website. ## Where this fits against building a forum yourself The alternative to this repository is to build the same product from parts, choosing a forum engine, adding a payment integration, wiring up messaging and building the admin console yourself. The difference in approach is worth naming precisely. Here you get a complete, working, Chinese market specific implementation. WeChat Pay for the mini program, H5 and App, WeChat mini program subscription messages, WeChat virtual payment for the member module, openid login, deepseek backed content generation, a points and wallet economy with withdrawal and billing, a reporting and review workflow, circles with join and leave management, and an admin console with role permissions. Each of those is a small project on its own, and together they are the bulk of the work in this kind of product. The cost of the approach is that you inherit all of it, including the parts you did not want: the Node 14 constraint, the front ends buried inside the backend static resources directory, the two parallel uni-app code bases, a websocket module that needed explicit cluster deployment work, and a database schema you cannot get without joining a chat group. For a developer learning how this category of product is put together, reading this code is more instructive than reading a framework. For a team shipping one, the decision comes down to the licence terms rather than the code. ## Conclusion Adopt linfeng-community as a reference if you are building a Chinese style community forum and want to study a complete Spring Boot and Vue implementation of posts, circles, private chat, payments and points rather than start from an empty project. Do not adopt it as a product you intend to run commercially, because the open source terms restrict it to personal study, forbid selling modified versions, and the repository itself omits the SQL scripts, which are distributed through a QQ group. Before you start, get the SQL files and the documentation from the group, confirm the Node version constraint of 14 or lower for the admin console, and set the source of truth for the code on the Gitee mirror, which the README says is updated first. ## FAQ ### How do I set up the linfeng-community forum? Configure MySQL 5.7 or higher and Redis, start Redis first and then the backend API service, run `npm install` and `npm run dev` for the Vue admin console with node version 14 or lower, and open the uni-app user client in HBuilderX after running `npm install` in its project root. The SQL files and documentation are distributed through the QQ groups listed in the README. ### What front ends does the linfeng-community repository contain? Three code bases inside the backend tree: the Vue admin console at src\main\resources\static\linfeng-community-vue, the uni-app Vue 2 user client at src\main\resources\static\linfeng-community-uniapp-ky, and the uni-app Vue 3 client at src\main\resources\static\linfeng-community-uniapp3-ky. The user client targets a mini program, H5, an App and a PC web product. ### Can I use the open source edition of linfeng-community commercially? No. The open source notice restricts the edition to personal study and research, prohibits modifying or selling the code and resources, and limits commercial use. The software is registered for copyright, and the README directs anyone needing commercial terms to the project website. ### Where do I find the SQL schema for linfeng-community? It is not in the repository. The README says the SQL files are distributed through the QQ group, and that the way to get them is to star the repository on GitHub and then join a group with your GitHub username noted. ## Sources - [Issues](https://github.com/virus010101/linfeng-community/issues) - [Project website](https://www.linfengtech.cn) - [README](https://github.com/virus010101/linfeng-community/blob/main/README.md) - [virus010101/linfeng-community on GitHub](https://github.com/virus010101/linfeng-community) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/virus010101-linfeng-community