How samseralikhan/medicine-tracker works
Project Type and Purpose
• This is a full-stack web application called “Medicine-Tracker.”
• Frontend: React single-page app for users to sign up, log in, view/add medicines.
• Backend: Spring Boot microservice exposing REST APIs for auth, user data, medicine CRUD.
• Persistence: Relational database accessed via JPA repositories (UserRepository, MedicineRepository).
• Deployment: Docker containers for client and server orchestrated by docker-compose.
File Structure
• Top-level:
• client/ – React app (src, public, build artifacts, Dockerfile)
• server/medtracker/ – Spring Boot service (pom.xml, Dockerfile, Java packages)
• docker-compose.yml – defines multi-container setup
• Frontend follows component/context/page organization.
• Backend uses layered pattern: controller → service → repository → model, plus security (JWT filter, config).
• Config files: client/.env, server src/main/resources/application.properties, Dockerfiles, Maven wrapper.
README
• Minimal, only project name. We infer features from code: JWT auth, protected routes (PrivateRoute.jsx), medicine management.
Detail
• Don’t stop at “Frontend” and “Backend.”
• Drill into sub-components: e.g., AuthController vs. MedicineController, Context providers in React, JWT utils, exception handler.
• Environment/config concerns: Docker Compose network, .env, application.properties.
Summary
• Within each container, break out modules/packages.
• Technologies, protocols, and data formats (JSON Web Token, JSON Payloads).