- Architecture Overview - Modular monolith layout, host-aware surfaces and the runtime topology
- Development Workflows - Local setup, build/test commands, branch strategy and CI/CD triggers
- DNS and Custom Domains - Cloudflare zones, App Service bindings and the proxied-mode decision
- Identity and Access - The identity model and the stubs left for the identity slice
- Infrastructure and Cost - Azure resources provisioned per environment and what they cost
Trip Side Kick is a travel itinerary planner: one place for flights, stays, bookings and day-by-day
plans that you can share with the people you are travelling with. It is an ASP.NET Core (.NET 10)
modular monolith that serves two surfaces from a single App Service deployment — a Razor Pages
brochure site on tripsidekick.net and a React + TypeScript progressive web app plus versioned
/v1 API on tripsidekick.app. Azure infrastructure is provisioned with Terraform onto the shared
platform-hosting App Service plan, with DNS in Cloudflare.
Please read the contributing guidance; this is a learning and development project.
Please read the security guidance; I am always open to security feedback through email or opening an issue.