How yae-sine/gustave-roussy works
Project type and purpose
• This is a full-stack web application called “Gustave-Roussey” for managing donations, subscriptions, and events.
• The backend is a monolithic Spring Boot REST API in Java 17.
• The frontend is a React 18 single-page application styled with Tailwind CSS and served via Nginx.
• Payments are processed through Stripe.
• The entire system is containerized and orchestrated with Docker Compose.
File structure
Top-level layout:
• Backend/ – Spring Boot project
– src/main/java/com/_com/JourneeMondiale/{controller, service, repository, model, dto, security, payload}
– application-properties, Dockerfile, pom.xml, Maven wrapper
• frontend/ – React project
– src/{components, pages, services, context, hooks}
– public/static assets, Tailwind config, Nginx config, Dockerfile
• docker-compose.yml – defines two services (backend & frontend), network, volumes
• .env.example – for Stripe keys and API URLs
Architectural patterns:
• Backend is layered (Controller → Service → Repository → H2 Database)
• JWT-based security filter chain in Spring Security
• RESTful endpoints for all user/admin actions
• React uses context for global user state and React Router for routing
• Nginx acts as reverse proxy and static file server
Extract insights from README
• REST API on port 8080, React app on port 80
• H2 file-based DB persisted via Docker volume
• Custom Docker network allows services to refer to each other by name
• Stripe integration for one-time donations and recurring subscriptions
Detail without over-complicating
• Every major Spring Boot module alongside the React service modules.
• Network boundaries (Docker network) and data persistence boundary (H2 volume).
• Surface security boundary: highlight JWT filter before reaching controllers.