How shubham996633/kuber-webstore works
Project Type and Purpose
• This is a full-stack, Kubernetes-based e-commerce provisioning platform (“Kuber WebStore”).
• Purpose: Provide a React dashboard and REST API to spin up isolated WooCommerce/WordPress stores on demand in a K8s cluster, using a Helm chart for deployment.
File Structure
• Top-level dirs:
• backend/ – Node.js + Express API in TypeScript, including routes, services (provisioner, recovery, guardrails, WooCommerce/Medusa integrations), K8s client wrappers, SQLite migrations.
• dashboard/ – React + Vite + TS + Tailwind UI, with components, API client, hooks.
• docker/ – Dockerfiles for API & dashboard, nginx.conf.
• helm/kuber-platform/ – Helm chart (templates for API & dashboard deployments, services, ingress, PVCs, RBAC, namespace).
• scripts/ – setup-local.sh, teardown.sh for k3d cluster orchestration.
• Key configs: Dockerfiles, helm/values-*.yaml, tsconfig.json, Vite/tailwind configs.
README for Additional Insights
• Architecture: Single-cluster multi-tenant pattern: one API+dashboard in “kuber-system” namespace, per-store dynamic namespaces (“store-<id>”) containing WordPress & MySQL pods + PVC + Ingress + NetworkPolicy.
• Tech stack: React 19, Node.js 22, Express 4, TypeScript, SQLite, @kubernetes/client-node, Helm 3, Traefik ingress.
Elements
• Rectangle (UI & API) in blue