How teoloop/nomadax works
Project type and purpose
• NomadaX is a full-stack, containerized web application for booking short-term accommodations (Airbnb-style).
• The user-facing SPA (React + Vite) communicates over REST with a Java Spring Boot backend, which persists data in MySQL.
File structure
• Top-level:
• backend/ (Spring Boot app + Dockerfile + Maven)
• frontend/ (React + Vite + Dockerfile)
• docker-compose.yml (orchestrates frontend, backend, MySQL)
• init/nomadaxbkp.sql (DB schema/data)
• backend/src/main/java/com/nomadax: layered MVC style
• config/ (SecurityConfig, WebConfig)
• controller/ (HotelController)
• service/ (HotelService)
• repository/ (IHotelRepository, IImageRepository)
• entity/ (Hotel, Image, Reservation, User)
• exception/ (handlers, custom exceptions)
• frontend/src:
• pages/ (HomePage, HotelDetailPage, HotelsPage, AdminDashboard)
• components/ (Header, Footer, SearchBar, AddHotelModal, etc.)
• services/hotelService.js (REST client)
README for additional insights
• Stack: Java + Spring Boot, React + Vite, MySQL, Docker, Docker Compose, Maven
• Features: public hotel listings, detail view, recommendations, admin CRUD panel
• Deployment: spun up via docker-compose on ports 3000 (frontend), 8080 (backend), 3306 (MySQL)
Essential elements
• Clearly separate layers (UI → API → Persistence)
• Ports (3000, 8080, 3306)
• Docker Compose orchestrating all containers
• Init/nomadaxbkp.sql volume mount for DB schema loading