How plantcareassistant-rncp/plantcareassistant works
Project type and purpose
• This is a full-stack web application (“PlantCareAssistant”) built with Next.js 13 (“app” directory), React components, and Supabase (database, auth, and storage).
• It exposes RESTful API routes under app/api/*, uses Prisma for schema/migrations, and ships as a Dockerized service (see Dockerfile and compose.yml).
File structure
• Top-level “plant-care-assistant” folder houses both frontend UI and backend API in a single Next.js monorepo.
• app/: Next.js App Router—the React pages, layouts, and serverless API endpoints (app/api/.../route.ts).
• components/: Reusable UI (common, features, forms, layout, UI modals).
• lib/: Supabase client wrappers for browser (supabaseClient.ts) and server (supabaseServer.ts).
• providers/: React context for Auth.
• prisma/ & supabase/: Database schema, migrations, RLS policies, and seed scripts.
• tests/: Unit tests for utils & API validation, E2E tests with Playwright.
• Dev-ops configs: Dockerfile, compose.yml, GitHub workflows for CI and Playwright.
README
• Minimal description (“RNCP Project – Plant Care Assistant”), implying the focus is on plant-care scheduling, social feed, user profiles, events, and image uploads via Supabase Storage.