How alunjax/halo works
Project Type and Purpose
• This is “Halo,” an open-source, full-stack, monolithic blog publishing application written in Java (Spring Boot).
• It serves both as backend (REST APIs, page rendering) and embeds a frontend admin UI (Freemarker templates & static resources).
Top-Level Architectural Layers
• Presentation Layer
• HTTP interface (controllers under app/controller) handling both admin UI and public content.
• Freemarker template engine (views under src/main/resources/templates).
• Business Layer
• Service classes (app/service + app/service/impl) implementing application logic.
• Caching and AOP aspects (app/cache, app/aspect) to optimize performance and apply cross-cutting concerns.
• Event-driven modules (app/event, app/listener) for decoupled actions (e.g., on comment, theme update).
• Data Access Layer
• Repositories (app/repository) using Spring Data JPA to talk to a relational database.
• Database migration scripts (src/main/resources/migration).
• Infrastructure & Integration
• File storage handlers (app/handler/file) for local or cloud object stores (AliOSS, Qiniu, etc.).
• Mail subsystem (app/mail) connecting to SMTP for notifications.
• Git-based theme fetcher/updater (app/theme) integrating with remote Git repos.
• Security filters & token services (app/security) managing authentication/authorization.
• Scheduled tasks (app/task) for maintenance (e.g., post cleanup).
External Dependencies & Services
• Relational Database (MySQL/Postgres/etc.)
• Cache store (in-memory or external, e.g. Caffeine/Redis)
• SMTP mail server
• Object storage (local FS or cloud OSS)
• Git repository host (for themes)
• Docker (deployment container)