How aadirathodprojects/infobell-devboard works
Project type and purpose
• This is a full-stack web application comprising:
• A React + TypeScript + Vite frontend that delivers a single-page app (SPA)
• A Go backend service exposing GraphQL (via schema.graphql) and gRPC interfaces (defined in devboard.proto)
• A PostgreSQL (or similar) database managed through SQL migrations
File structure
• Top-level separation:
• frontend (implicit): package.json, vite.config.ts, src/, public/, index.html
• backend: backend/cmd/server/main.go, backend/internal/{config,db,service}, backend/migrations, backend/proto, backend/schema.graphql
• Architectural hints:
• cmd/server → entry point for HTTP/gRPC server
• internal/config → centralized configuration loader
• internal/db → DB client, ORM/models, migration scripts
• internal/service → business logic layer
• proto + schema.graphql → API contracts for gRPC and GraphQL
Key README insights
• The README focuses on the Vite + React + TypeScript setup with ESLint, but does not describe the Go backend.
• We infer the backend is a separate Go module (go.mod) and uses SQL migrations plus protocol definitions.