How misterivanzik/ecodeli-2a5-zazic-lisika-tafili works
Project type and purpose
• EcoDeli is a modular, full-stack web application.
• Frontend: Vue.js 3 single-page application (SPA)
• Backend: Spring Boot 3 RESTful API
• Database: MariaDB
• Purpose: connect merchants, service providers, couriers and customers in a sustainable delivery ecosystem.
File structure
• Top-level directories
• ecodeli-frontend: Vue.js SPA (components/, views/, router.js, store/)
• ecodeli-backend: Spring Boot service (controllers/, services/, repositories/, models/, security/)
• Backend patterns
• MVC-inspired layering:
– Controllers handle HTTP endpoints
– Services encapsulate business logic
– Repositories manage data persistence
• Security: JWT filter and config class
• Configuration: application.yml / properties, Maven wrapper
• Frontend patterns
• Component hierarchy: layout/Header.vue, DeliveryMap.vue
• View segmentation by user roles (admin, client, livreur, prestataire)
• Global state (store/auth.js) and API services (apiServices.js, authServices.js)
• Routing: defined in router.js
• Build: package.json, vite.config.js
README for additional insights
• Environment variables: DB connection, JWT secret, mail SMTP settings
• External dependencies: MariaDB, SMTP mail server, geocoding API hinted by GeocodingService
• Swagger API docs available at /swagger-ui
• Goals: modularity, security, maintainability, sustainability
Final recommendations
• Avoid overcrowding: collapse less relevant docs or legacy modules into “Documentation” or “Admin Tools”