How beastofshadow/mobishare works
Project type and purpose
• This is a full-stack web application (monolithic ASP NET Core Razor Pages) with a layered architecture.
• Purpose: “Mobishare” is an urban mobility platform that allows users to locate, reserve, and ride standard bikes, e-bikes, and scooters. It provides real-time map updates, telemetry via MQTT, chat support, payments via PayPal, and Google OAuth authentication.
File structure
• Top-level solution contains four main projects:
• Mobishare.App – the ASP NET Core Razor Pages web application (UI + Web API endpoints + SignalR hubs + hosted services).
• Mobishare.Core – domain models, EF Core DbContext, request/response DTOs (CQRS style), validation attributes, security policies.
• Mobishare.Infrastructure – implementations of external-facing services (Google geocoding, AI chatbot, MQTT, SignalR hubs).
• PayPal.REST – a wrapper for PayPal REST APIs.
• Mobishare.Tests – automated tests.
• Web UI: Razor Pages under Areas/Admin, Areas/Identity, and /Pages. Static assets under wwwroot (CSS, JS, Bootstrap, jQuery).
• Configuration: appsettings.json, launchSettings.json, environment variables for OAuth, API keys, PayPal.
• Data: EF Core migrations under Core/Migrations, using SQLite.
• Real-time & messaging: SignalR hubs (ChatHub, VehicleHub, TimerHub) and MQTT hosted services.
README
• Confirms tech stack: Razor Pages, ASP NET Core, SQLite, SignalR, OAuth, PayPal, MQTT, Google Maps, AWS.
• Describes user/admin flows and required environment variables.
Detail & essential elements
• Don’t simply list files; capture logical components: UI, API, business logic, data, and integrations.
• How data flows end-to-end: from user click → server handler → database → back to user / SignalR client.
• Hosted services polling MQTT and pushing updates to hubs.
• Environment/configuration boundary for keys and secrets.