How erencanakyuz/airportsystem works
Project type and purpose
• AirportDemo is a full-stack ASP.NET Core 9.0 MVC web application (“Airport Detective Nexus”) for real-time flight tracking, fuel management, logistics, maintenance dashboards, and flight control, backed by EF Core and SQLite.
File structure
• Top-level layers:
• Controllers (MVC controllers and a SignalR Hub for real-time updates)
• Views (Razor Views organized by feature: Flights, Radar, Maintenance, Auth, Shared)
• Data (ApplicationDbContext + EF Core Migrations)
• Models (Domain & view models: Flight, User, Login/Register)
• Program.cs (app startup, DI, middleware, SignalR endpoints)
• Configuration: appsettings.json
• Static assets under wwwroot (CSS, JS, libraries)
• airport.db (SQLite database file)
• Build/deployment artifacts (bin/, obj/) and CI workflow (.github/workflows/dotnet.yml)
Extract architectural insights from the README
• Uses ASP.NET Core MVC, EF Core → relational DB layer
• Razor to render dynamic views
• SignalR Hub (FlightHub) for pushing real-time flight data to clients
• External/3rd-party integration: RadarApiController may call external radar API to fetch flight positions
• LoggingHandler indicates custom middleware or HTTP message handler for request logging
Main components and their interactions
a. UI Layer (Browser)
• Razor Views + static assets (CSS/JS)
• JavaScript client connects to SignalR FlightHub for live updates
b. Web Server / Application Layer
• ASP.NET Core MVC pipeline:
• Routing → Controllers
• Middleware: LoggingHandler, Authentication (AuthController)
• Controllers: FlightsController, RadarController, MaintenanceController, FuelManagement, Logistics
• SignalR Hub: FlightHub for real-time push
c. Business/Data Layer
• ApplicationDbContext (EF Core)
• Models → mapped to SQLite tables
d. Data Storage
• SQLite DB file (airport.db) with EF Migrations
e. External Services
• RadarApiController calls external flight radar API
• (Future) predictive analytics module for runway positions
f. Authentication & Authorization
• ASP.NET Identity or custom auth (AuthController with Register/Login view models)
Architectural patterns and design principles
• MVC (Models ↔ Views ↔ Controllers)
• Repository pattern implicit via DbContext
• Real-time event broadcast via SignalR Hub
• Separation of concerns: Controllers orchestrate, Data layer persists, Views render
• Middleware pipeline for cross-cutting concerns (logging, error handling)