How dinexh/filesharingsystem works
Project Type and Purpose
• This is a full-stack file-sharing web application.
• Frontend: React single-page app (SPA) providing authentication, upload/download UI, file browsing, theming.
• Backend: Spring Boot REST API that handles auth (JWT), file operations, user management, sharing logic, email notifications.
• Persistence: MySQL stores user and file metadata; filesystem “uploads” directory stores physical file blobs.
• External service: SMTP server for sharing notifications.
Main Components
a. Client (React SPA)
• Pages: auth (login/signup/reset), dashboard (home, files, shared, profile, settings, upload), home.
• Components: Header, Sidebar, FilesList, PDFViewer, ShareModal, ProfileForm, etc.
• Contexts: AuthContext, ThemeContext.
• Utilities: fileUtils.
b. API Layer (Spring Boot Controllers)
• AuthController, FileController, UserController, PasswordResetController.
c. Service Layer
• Business logic: UserService, FileService, EmailService, CustomUserDetailsService.
d. Persistence Layer
• Repositories using Spring Data JPA: UserRepository, FileRepository, FileShareRepository, StarredFileRepository.
• Entities: User, File, FileShare, StarredFile.
e. Security
• Stateless JWT filter chain: JwtAuthenticationFilter, JwtAuthenticationEntryPoint, JwtTokenProvider, SecurityConfig.
f. Database
• MySQL storing tables for users, files, shares, starred files.
g. File Storage
• Local filesystem directory (“uploads”) with UUID-renamed files.
h. External SMTP Service
• Configured via Spring Mail for notifications.
Relationships and Data Flows
• Browser ↔ React UI: user actions trigger API calls via fetch/axios.
• React UI ↔ Spring Boot API: HTTPS requests carrying JWT in Authorization header after login.
• Spring Boot Controllers delegate to Service layer.
• Service layer
• calls Repository layer (JPA) → MySQL
• reads/writes file blobs on filesystem
• uses JwtTokenProvider for token generation/validation
• invokes EmailService → SMTP server
• Security filter intercepts incoming requests to validate JWT and inject SecurityContext.
Architectural Patterns & Principles
• Layered architecture (Controller → Service → Repository).
• MVC-style separation in backend.
• Stateless REST with JWT for scalability.
• Single Page Application (SPA) architecture in frontend.
• Context API for global state (auth, theme).
• Responsiveness and theming on client.
Technologies & Frameworks
• Frontend: React, Context API, CSS modules, create-react-app tooling (webpack).
• Backend: Spring Boot, Spring MVC, Spring Security, Spring Data JPA, Maven, Java 11.
• Database: MySQL.
• File storage: Local filesystem.
• Email: Spring Mail (SMTP).
• Security: JWT.