How qazuor/hospeda works
Project type and purpose
• This is a full-stack, monorepo-based tourist accommodation platform (“Hospeda”) built with TurboRepo.
• It provides a public website (Astro + React) for browsing destinations, accommodations, events, and a backend API (Node.js + Hono) for data access and admin management.
File structure
• Top-level “apps” folder:
• apps/api → Hono-based REST API with versioned routes (public & admin), middleware, utils, and type definitions.
• apps/web → Astro-powered SSR/SSG frontend, using React components and a TanStack‐Router data-fetching layer.
• apps/react-app-testing → sample React/Vite playground (for component testing).
• Shared “packages” folder:
• packages/db → Drizzle ORM database layer (models, migrations, seeds, service classes).
• packages/schemas → Zod validation schemas for all entities.
• packages/types → TypeScript definitions for entities and enums.
• packages/logger → centralized logging library.
• packages/utils → generic utilities.
• packages/config, typescript-config, tailwind-config, ui → shared tooling, styling, and UI primitives.
• Config & scripts: CI workflows (.github), Dockerfile.api, TurboRepo config (turbo.json), PNPM workspace.
README for extra clues
• Confirms tech stack: Astro + React + Tailwind on frontend, Node + Hono + Drizzle + PostgreSQL on backend.
• Mentions multi-tenant roles & permissions, migrations, seeds, and DevOps targets (Fly.io deployment).
a. Main components
• Frontend (apps/web)
• Backend API (apps/api)
• Database (PostgreSQL via packages/db)
• Shared libraries (packages/logger, schemas, types, utils, ui, config)
• External services (e.g., Fly.io hosting, Drizzle Studio)
b. Relationships & data flows
• Browser → Web (HTTP GET/POST)
• Web → API (REST calls to /v1/public & /v1/admin endpoints)
• API → DB (Drizzle ORM queries & transactions)
• API & Web → Shared packages (importing types, schemas, utils)
• API logs → packages/logger → console/file/external logging sinks
c. Architectural patterns & principles
• Monorepo with TurboRepo for builds & dependency graph
• Layered backend: middleware → routes → controllers/services → ORM
• Repository & service pattern in DB package
• Declarative component-based UI in Astro/React
• Shared contract-first validation (Zod schemas) and types across layers
d. Technologies & frameworks
• Frontend: Astro, React, TanStack Router, Tailwind CSS, Vite
• Backend: Node.js, Hono, Zod, Drizzle ORM, PostgreSQL
• Tooling: TurboRepo, PNPM, Biome (lint/format), Fly.io (deploy)
Key details to capture
• Versioned route separation (public vs. admin) in the API
• Middleware chain (auth, error handlers, logger)
• Drizzle ORM’s migration/seed process
• Shared Zod schemas/types ensuring contract alignment
• Monorepo build coordination (Turbo → PNPM filters)