How yougotnothing/inspace works
Project type and purpose
• This is a full-stack, microservices-style web application (“InSpace”) that aggregates and displays space events (moon phases, eclipses, meteor showers, etc.), air and light pollution data, and lets users “spot” events and receive email notifications.
• The stack comprises:
• A GraphQL backend (NestJS + Prisma + PostgreSQL + Redis + MinIO + SMTP/email)
• A React/Apollo/Vite frontend
• A Python FastAPI microservice (OAuth flows & geolocation routes)
• Docker/Docker-Compose for orchestration
File structure
Top-level folders:
• api – NestJS GraphQL server with modules for auth, events, pollution, geolocation, email, user profiles, file uploads (MinIO), Redis caching, Prisma migrations/schema, Pug email templates, GraphQL schema/resolvers.
• frontend – React SPA using Apollo Client, Vite, styled-components, custom hooks, TypeScript types, validation schemas.
• python – FastAPI service handling external OAuth (Google, GitHub, OpenID Connect/Keycloak) and geolocation routes.
• docker-compose.yml – ties together API, frontend, Python service, Postgres, Redis, MinIO, Keycloak (via wait script).
README for additional insights
• Clearly states project idea and feature set (GraphQL integration, three.js UI, email, OAuth, “toSpotted”).
• Tech badges show NestJS, Prisma, React, GraphQL, Apollo, FastAPI, Docker, etc.
• In-process checklist reveals which features are live.
Additional details to enhance informativeness
• Sequence: User logs in → Apollo sends login mutation → Auth module issues JWT → Redis stores session → Frontend stores tokens.
• How Prisma migrations evolve the DB schema over time.
• Three.js starfield & moon render as part of the Frontend’s UI component.
• “toSpotted” flow: user marks event → GraphQL mutation → Event module persists spotted flag → Notification module sends email if new.