How kaylaoneal/novel-plus-view works
Project type and purpose
• This is a full-stack, multi-module Java Spring Boot “monorepo” containing several coordinated subsystems:
• novel-front: public portal + writer console
• novel-admin: platform backend management
• novel-crawl: crawler + crawl‐management UI
• novel-common: shared DTOs, mappers, caches, utilities
• templates: multiple front-end theme templates
• It implements a CMS for original novels (search, browse, read, comment, pay), plus a pluggable crawler, multi-theme templating, sharding, caching, and optional external storage (OSS).
File structure
• Top-level: parent pom.xml, modules directories, docker-compose.yaml.
• Each module (novel-front/admin/crawl) is a Spring Boot microservice structured in MVC layers:
• src/main/java/com/java2nb/.../controller
• service & impl
• dao/mapper (MyBatis XML)
• domain/entity
• novel-common contains shared entities, mappers (MyBatis Dynamic SQL), caching (Redis), and utilities.
• Dockerfiles & build scripts under each module’s build/docker and a root docker-compose.yaml orchestrate MySQL, Redis, and the three Spring Boot services.
• templates folder holds static Thymeleaf templates for various themes.
README for technical stack
• Spring Boot, Thymeleaf, MyBatis (+ Dynamic SQL + Generator), PageHelper, Sharding-JDBC
• Caching: Redis
• Auth: JWT / Spring Security / Shiro
• Storage: MySQL (sharded) + optional Aliyun OSS for media
• Packaging/Deployment: Docker & Docker Compose
• UI: Layui / Bootstrap / custom static assets in each module