How savemos/fleetfra works
Project type and purpose
• From the file tree and README, this is a full-stack, turn-based “Battleship”-style game called FleetFra.
• Frontend: static HTML/JS/CSS under src/main/resources/static
• Backend 1: Java Spring-style REST API + WebSocket entry point under src/main/java
• Backend 2: Erlang/OTP‐based game engine under src/main/fleetfra_chin
• Reverse proxy / load balancer: NGINX (src/main/NGINX)
• Database: relational store via JDBC (FleetFra.sql, DAO layer)
File structure
• Top-level:
• pom.xml, mvnw → Maven build for Java
• src/main/NGINX → NGINX configuration and install docs
• src/main/fleetfra_chin → Erlang OTP application with rebar.config
• src/main/java/it/unipi/dsmt/FleetFra → Java controllers, services, DAOs, DTOs
• src/main/resources/static → HTML/JS/CSS UI
• src/main/resources/application.properties → DB connection, app properties
• Testing: JUnit tests for Java and a Java‐level websocket test
• Documentation: PDF in Documentation/
Key README insights
• User flows: login (player/admin), ship placement, game turn, end condition