How tejas1730/enotes works
Project type and purpose
• This is a full-stack web application built with Spring Boot.
• Purpose: allow users to register, log in, manage profiles, and create/read/update/delete “e-notes” with persistent storage and secure authentication.
File structure
• Top-level:
• pom.xml, Maven wrapper → build and dependency management
• src/main/java/com/enotes → Java code
– config: Spring Security and custom user details
– controller: MVC controllers handling HTTP requests and returning Thymeleaf views
– service: business logic interfaces and implementations
– repository: Spring Data JPA interfaces for CRUD
– entity: JPA-annotated domain models (User, Note)
– EnotesSpringBootApplication.java → entry point
• src/main/resources
– application.properties → DB and JPA config
– static → CSS/JS/images
– templates → Thymeleaf HTML views
• src/test → JUnit tests for application context
README for additional insights
• Confirms use of Java 17+, Spring Boot, Spring Data JPA, Spring Security, Hibernate, Thymeleaf, and a relational DB (MySQL/PostgreSQL).
• Core features: secure user registration with email uniqueness, BCrypt password handling, CRUD on e-notes.
Detail
• Security as its own module with its interaction path on every HTTP request.
• Thymeleaf templates under “Views” and static assets as a sibling to illustrate how the client receives HTML/JS/CSS.
• Main application class as the “bootstrap” component that wires everything together.