How vignesh-d-2003/e-books-project works
Project type and purpose
• This is a full-stack e-Library application. The frontend is built with Next.js (in the top-level src/app directory), providing server-side-rendered pages and client-side components for user authentication, book browsing, and an admin dashboard.
• The backend is a Spring Boot service (in the E-Library/ folder) exposing REST endpoints for user, book, category, and file operations, using JWT for authentication and Supabase as the external database and file-storage provider.
File structure
• Top level:
• Next.js app under src/app, src/components, src/context, src/services
• Spring Boot app under E-Library/src/main/java/com/example/E_Library
• Build/config files: package.json, next.config.mjs, pom.xml, .env, .mvn, etc.
• Patterns:
• Frontend follows the Next.js App Router (page.js files for routes) and a context-/service-based API layer (AuthContext.js, bookService.js, etc.).
• Backend uses MVC: controllers → services → utilities, with cross-cutting concerns handled by aspects and filters (LoggingAspect, MdcFilter, JwtRequestFilter).
• Deployment/config: environment variables in .env, CORS and security in configuration/, logging via logback-spring.xml.
README for additional insights
• Bootstrapped with Create Next App for the front end, deployed on Vercel by default.
• No explicit architectural docs in the README, so infer from file layout and naming conventions.