How solidarityhub-organization/solidarityhub works
Project type and purpose
• This is a full-stack emergency-management application named SolidarityHub.
• Frontend: Flutter apps targeting mobile (App/), desktop (Desktop/), web, Linux, macOS, Windows, and iOS.
• Backend: ASP.NET Core Web API (“LogicPersistence.Api”) with Entity Framework Core migrations, layered into Controllers → Services → Repositories → Database.
File structure
• Frontend “App/” and “Desktop/” share a Flutter-style layout:
• lib/controllers, models, services, interface/screens, widgets → UI and business-logic layers.
• Platform folders (android/, ios/, linux/, macos/, windows/, web/) contain build configurations and native bootstrap code.
• Backend “Backend/LogicPersistence/LogicPersistence.Api/”:
• Controllers/ expose REST endpoints.
• Services/ contain business logic and Observer-pattern notifications.
• Repositories/ (and Interfaces/) abstract data persistence via EF Core.
• Models/ domain entities, DTOs, mappers, intermediate models.
• Migrations/ define database schema evolution.
• appsettings.json, Docker-compose in Backend/ for Postgres container.
Additional insights from README
• Frontend connects to backend via HTTP to Postgres-backed API.
• Docker-compose is used to spin up Postgres for development.
• Environment variables (.env.development) hold database credentials.
Detail
• ObserverPattern sub-component under Services for notifications.
• Migrations path and configuration files (appsettings.json, Docker-compose.yml).