How cherryshine/pashare works
Project type and purpose
• PaShare is a monolithic, full-stack web application built on Spring Boot.
• It follows a classic server-side MVC pattern with Thymeleaf templates for the UI, a REST-style API for text operations, persistent storage in MySQL, JWT-based admin auth, and Cloudflare Turnstile CAPTCHA integration.
File structure
• Top-level build files (build.gradle, Gradle wrapper) → standard Spring Boot build.
• src/main/java/com/jeesoo/pashare:
• config/ (WebConfig) → servlet mappings, resource handlers
• controller/ (MainController, TextController, AdminController, CaptchaController) → HTTP endpoints
• service/ (TextService, AdminService) → business logic
• repository/ (TextRepository) → Spring Data JPA interface to MySQL
• entity/ (Text) → JPA @Entity model
• filter/ (TurnstileCaptchaFilter) → pre-controller CAPTCHA validation
• util/ (JwtUtil) → JWT generation/validation
• dto/ → request/response payload classes
• src/main/resources:
• templates/ (Thymeleaf HTML views: index, shared-text, admin, turnstile)
• static/ (assets, site.webmanifest)
• src/test/java → integration/unit tests
README for additional insights
• Confirms use of Spring Boot 3.x, Spring Data JPA, MySQL, Thymeleaf, JWT, Cloudflare Turnstile.
• Describes key REST endpoints (/api/save-text, /api/get-text, /api/share-via-link, admin APIs, CAPTCHA API).
• Notes admin panel UI, 24-hour link expiry logic, 4-digit code sharing.
Essential architectural elements
• Validity window (24h link expiry) as a note on the “share-via-link” flow.
• Security-sensitive flows (admin login → JWT issuance → JWT-protected endpoints).