How malikyakub/alisom-online-market works
Project type and purpose
• This is a full-stack e-commerce web application (“Alisom online market”) built as a single-page React/TypeScript front-end that uses Supabase as its backend (authentication, database, storage).
• The app provides both an Admin interface (product/category management, dashboards, customer listings) and a User interface (browsing, cart, checkout, account management).
File structure
• Top-level config: Dockerfile, .dockerignore, Vite config, tsconfig.json, package.json.
• Front-end code under app/ – follows a Remix-style or React-Router folder-based routing convention (app/routes/...).
• UI components in components/; reusable hooks in hooks/; Supabase setup in utils/supabase.ts; static assets under public/assets.
• No custom backend code – the application relies entirely on the Supabase service.
README
• Focuses only on local setup and running the Vite dev server.
Main components
a. Client Application (React/TypeScript SPA)
• Routing Layer (app/routes) – Admin and User sub-routes
• UI Components library
• Business Logic/hooks layer (useAuth, useProducts, useUsers)
• Asset Delivery (public/assets)
b. Backend as a Service (Supabase)
• Authentication service
• PostgreSQL Database
• Storage (for images/assets if used)
c. DevOps / Deployment
• Vite dev server for local development
• Docker container (Dockerfile) for production build
• Hosting platform (e.g., Vercel, Netlify, self-hosted Docker)
Relationships and interactions
• Client → Supabase Auth: sign-up, login calls via Supabase SDK
• Client → Supabase Database: CRUD operations for products, categories, orders
• Client → Supabase Storage: optional fetch/upload of product images
• DevOps Pipeline → Docker build → Container Registry → Hosting
Architectural patterns & design principles
• Folder-based routing (React Router / Remix-style) to separate features
• Separation of concerns: UI in components/, data-fetch logic in hooks/, routing in app/routes/
• BaaS integration (no custom backend) for faster time-to-market and scalability
• Containerization for environment parity (local vs production)
Essential elements
• Component boundaries and labels