bbs-springboot: a Spring Boot forum backend with articles, Q&A and role-based permissions

bbs-springboot is the Java backend of a two-repository forum deployment

bbs-springboot (Nan's BBS, version 3.0.0) is one half of a front-back separated forum system: this repository holds the Spring Boot service, and the Vue frontend lives in a separate repository named bbs-vue-ui. Cloning bbs-springboot gives you only the Java backend. A working forum requires both repositories deployed and configured independently, and the deployment guides treat them as separate projects.

At the top level, the repository contains four Maven module directories: bbs-article/, bbs-common/, bbs-rest/, bbs-user/, plus a db/ directory for database initialization files and a pom.xml. No single-command quick start appears in the README. Instead, deployment instructions are external, hosted as separate articles on the project's own site.

The project was built to address a specific gap in the Chinese Java ecosystem: most open source community platforms are written in PHP, and Spring Boot or Spring Cloud variants are rare. Companies that use Java internally face integration friction with PHP-based alternatives. bbs-springboot targets Java enterprise teams that want a developer forum they can integrate with their existing Spring Boot infrastructure.

Deployment documentation lives at bbs.nansin.top and the README screenshots come from the commercial build

No build command, required Java version, database configuration, or default port appears in this repository's README. Backend deployment instructions are hosted at bbs.nansin.top/detail/44 and frontend instructions at bbs.nansin.top/detail/45. A video walkthrough is on Bilibili at the URL the README links to. No prebuilt packages are published to GitHub, so a deployment tracks a branch commit rather than a pinned artifact.

Two separate live environments exist. An open source demo runs at open.nansin.top, with public registration open to new users and admin credentials listed in the README as 椿/123456. A commercial demo with fuller permission controls runs at bbs-corp.nansin.top.

A detail worth reading carefully: the README's static screenshots section opens with the note that it shows only partial effects, and points to the commercial demo for the full experience. That means the screenshots in the README are drawn from the commercial build, not from the open source code in this repository. A team evaluating features from those screenshots is looking at a different deployment than what they would run.

Forum content divides into three types: articles, Q&A and topics

The user-facing forum provides three distinct content types. Articles (文章) are long-form posts. Q&A entries (问答) are question-and-answer threads. Topics (话题) are discussion posts. Each appears as a separate section of the forum with its own list view and creation flow.

Alongside those content types, several supporting systems are visible in the screenshots. A points system (积分系统) tracks user activity and reputation across the forum. A message notification system (消息通知) delivers alerts when users receive replies or mentions. A creator center (创作中心) gives authors a single view for managing their published content. Personal homepages display each user's profile and content history, and a theme switcher lets users toggle the visual style.

Forum management also exists as an admin view within the user system, separate from the main Nan's Operations permissions layer. The README says the project took design cues from Juejin (稀土掘金) and Bilibili. Whether the open source code includes all of those feature areas or whether some are reserved for the commercial version is not stated in the README.

Role and permission management live in a separate deployment called Nan's Operations

The project divides into two deployable parts. Nan's BBS covers content and user interaction. Nan's Operations (南生运营) handles role and permission management and runs as a separate service, reachable at manage.nansin.top in the live demo.

Screenshots of the admin system show eight areas: a dashboard, organizational structure management, system management, role management, menu configuration, user management, an access log, and a forum management view. The commercial demo at bbs-corp.nansin.top is described in the README as providing the full permission control experience. The open source demo at open.nansin.top provides admin access through the 椿/123456 credentials but does not claim to show the complete feature set.

For an organization that needs fine-grained access control, having a dedicated permissions service is an architectural choice with operational implications. Two services to deploy, monitor and upgrade means more overhead than a single-application deployment, and the README does not address that cost.

Spring Boot 2.x and 3.x each have a dedicated long-term support branch

Three branches serve different maintenance goals. The master branch carries the latest Spring Boot 3.x code. LTS-SpringBoot3 is the long-term support branch for Spring Boot 3.x, and the README notes it is currently identical to master. LTS-SpringBoot2 is the long-term support line for Spring Boot 2.x.

Teams that have not upgraded to Spring Boot 3.x can follow LTS-SpringBoot2 without being forced to migrate. Teams on Spring Boot 3.x have two options: the rolling master branch or the more stable LTS-SpringBoot3. The README does not document what triggers a merge from master to LTS-SpringBoot3 or what guarantees the LTS label carries.

A Spring Cloud Alibaba option is named in the README as a third backend choice, linked to a comparison page at bbs.nansin.top/detail/641. That option is in a different repository; bbs-springboot covers only the two Spring Boot branches. On the frontend side, bbs-vue-ui provides separate implementations for Vue 2 with Ant Design and Vue 3 with Element Plus. The README directs readers to the comparison page rather than documenting which backend branch pairs with which frontend version.

Where this project fits and where it does not, including the authorization question

bbs-springboot is aimed at Java teams inside organizations that want a developer community with managed permissions. Its documentation, README, and deployment guides are all in Chinese, which creates an immediate barrier for teams that work in other languages. A team without Chinese-language reading ability faces a real friction point before a first deployment.

For a non-Java community platform with English documentation and self-hosted or managed hosting options, Discourse is a well-known alternative. Discourse uses a Ruby on Rails backend and an Ember.js frontend, with a fully documented Docker-based install path. The architectural difference is significant: Discourse is a monolith with an established upgrade path, while bbs-springboot is a multi-module Maven project that requires coordinating a separate frontend repository and a separate permissions service.

AGPL-3.0 is the stated license, and the README separately requires company or commercial use to obtain author authorization at bbs.nansin.top/detail/600 in addition to complying with the license terms. The last push was on 2026-07-22 and the repository carries no GitHub release tags.

What the two demo environments reveal about the open source and commercial tiers

Having two separate demo environments is unusual for an open source project, and the distinction the README draws between them is informative. The open source demo at open.nansin.top is available for public registration and admin login. The commercial demo at bbs-corp.nansin.top is described as showing the full permission control experience, with the README providing its credentials as 马亮南生/123456 for super-admin access.

The screenshots section reinforces that division. Each screenshot group ends with a reminder to visit the commercial demo for the full experience. This explicitly positions the open source demo and the screenshots themselves as illustrating only part of what the platform does. A team that evaluates bbs-springboot from the screenshots without also reading the README's notes on what the commercial tier adds may build incorrect assumptions about what the open source code includes.

The project description names it an enterprise-grade microservice open source project, but the boundary between open source and commercial features is not documented in the repository. The deploy guides at bbs.nansin.top and the contact channels (WeChat: maliangnansheng, QQ: 924818949) are the resources for resolving questions that the README leaves open.

Editorial conclusion

Use bbs-springboot when your team works in Java and Spring Boot, you need a forum with articles, Q&A, topics, and a separate permissions system, and you are prepared to deploy both this backend and the bbs-vue-ui frontend from two independent repositories. Skip it if you need a single-repository deployment, a project with no separate commercial authorization layer, or English-language documentation for onboarding. Before any commercial deployment, contact the author at bbs.nansin.top/detail/600 and get written clarification on how the authorization requirement applies to your specific use case.

Frequently asked questions

Official sources

1. Issues
2. License: AGPL-3.0
3. maliangnansheng/bbs-springboot on GitHub
4. Project website
5. README