How lampspace/swarm-drones-web-system works
Project type and purpose
• This is a full-stack web application called “Swarm Drone Websystem.”
• Frontend: Next.js (React)
• Backend: Laravel (PHP)
• Purpose: control and monitor a swarm of drones via a web UI, communicate with drones (ROS), persist data in a database, expose REST APIs for CRUD operations on users, swarms, missions.
File structure
• Top-level folders:
• api/ → Laravel application (app/, config/, routes/, resources/, tests/, Dockerfile, .env)
• frontend/ → Next.js app (pages/, components/, services/, assets/, Dockerfile, .env)
• nginx/ → reverse proxy configuration
• docker-compose.yml → orchestrates nginx, api, frontend, database
• The Laravel “app/Services” and “app/Models” directories point to a service-layer and MVC pattern.
• The Next.js folder contains pages/ (SSR/SSG routes), components/, hooks/ (including a ros.js hook for WebSocket to ROS).
• Infrastructure concerns (Dockerfiles, compose, nginx) Live at the root and in each service directory.
README for additional insights
• Indicates Docker Compose hosts: drones.svute.test → frontend, api-drones.svute.test → API.
• Uses Laravel Sanctum for auth, likely a MySQL container, maybe Redis for queues/caching (check docker-compose.yml).