dm-chelupati/grubify

Purpose and Entry Points

Grubify is a containerized food-delivery demo: a React single-page frontend drives a .NET 9 REST API for restaurant browsing, cart management, checkout, and order tracking. Runtime entry points are GrubifyApi/Program.cs for the API and grubify-frontend/src/index.tsx for the browser app. Azure Developer CLI deployment is defined by azure.yaml.

Frontend Application

The React 18/TypeScript client composes the delivery flow from page-level views: discovery, restaurant menus, cart, checkout, and tracking. Routing/application composition is centralized in grubify-frontend/src/App.tsx; page stages reside under grubify-frontend/src/pages/HomePage.tsx, grubify-frontend/src/pages/CheckoutPage.tsx, and grubify-frontend/src/pages/OrderTrackingPage.tsx. Shared navigation is in grubify-frontend/src/components/Navbar.tsx.

Frontend-to-API Boundary

Browser-side API access is centralized in grubify-frontend/src/services/api.ts, with shared client-side domain types in grubify-frontend/src/types/index.ts. This is the principal integration boundary: UI pages should consume the service layer rather than directly coupling to backend routes. The production frontend is containerized and served through Nginx via grubify-frontend/Dockerfile and grubify-frontend/nginx.conf.

API Host and HTTP Surface

The ASP.NET Core Web API host configures the HTTP pipeline and service startup in GrubifyApi/Program.cs. Controllers expose resource-oriented endpoints for the delivery workflow: restaurants and menus in GrubifyApi/Controllers/RestaurantsController.cs and GrubifyApi/Controllers/FoodItemsController.cs; carts and orders in GrubifyApi/Controllers/CartController.cs and GrubifyApi/Controllers/OrdersController.cs. WeatherForecastController.cs is a template/diagnostic-style endpoint, not part of the delivery domain.

Domain State and Workflow

Core API data contracts are Restaurant, FoodItem, Cart, and Order under GrubifyApi/Models/Restaurant.cs, GrubifyApi/Models/Cart.cs, and GrubifyApi/Models/Order.cs. The primary flow is: retrieve restaurants/items, construct or update cart state, create an order during checkout, then retrieve order status for tracking. No persistence layer, database project, or external payment provider is represented in the supplied tree; model/controller behavior is therefore the effective application-state boundary.

Container and Azure Deployment

Both application tiers build as separate images using GrubifyApi/Dockerfile and grubify-frontend/Dockerfile. Azure infrastructure is provisioned with Bicep: infra/main.bicep coordinates resources, while infra/core/host/container-registry.bicep and infra/core/host/container-app.bicep define image registry and Container Apps hosting. The target platform includes Azure Container Registry, Azure Container Apps, and a Container Apps Environment; the README also identifies Log Analytics as deployed observability infrastructure.

Operations and Automation

The repo is designed for Azure SRE-agent investigation scenarios, including stated memory-leak and payment-failure testing goals. GitHub Actions automation is defined in .github/workflows/sre-agent-investigate.yml. Deployment requires Docker for image builds plus Azure Developer CLI and Azure CLI; the prerequisite validation entry point is scripts/check-prerequisites.sh.