How suyogshelke/gamer-in works
Gamer-IN (GameRIN) is a full-stack social platform for gamers. Users register or sign in, then discover games and communities, publish and interact with media posts, follow creators, and view profiles, notifications, and achievements. The React app routes these experiences to an Express API; backend handlers use MongoDB-backed models, with shared services for feeds, notifications, and progression. The README establishes the platform capabilities, while source excerpts and the index show selected wiring; links for unsampled features are limited to documented relationships.
Main entry points: models Domain models · routes API routing · postController.js Posts and comments · progressionService.js Progression
Components 18
Web application
- Route application
frontend/src/App.jsx - Auth state
frontend/src/context/AuthContext.jsx - Product screens
frontend/src/pages - API client
frontend/src/services/endpoints.js
API layer
- API routing
backend/routes - Authentication
backend/controllers/authController.js
Social capabilities
- Posts and comments
backend/controllers/postController.js - Communities
backend/controllers/communityController.js - Profiles and follows
backend/controllers/userController.js - Game discovery
backend/controllers/gameController.js - Global search
backend/controllers/searchController.js - Achievements
backend/controllers/achievementController.js - Feed shaping
backend/services/feedService.js - Progression
backend/services/progressionService.js - Notifications
backend/services/notificationService.js
Persistence
- Domain models
backend/models - MongoDB
Other components
- Gamer
Connections 32
- Gamer → Route application: uses
README.md - Route application → Product screens: routes to
frontend/src/App.jsx - Route application → Auth state: checks session
frontend/src/App.jsx - Auth state → API client: loads identity
frontend/src/context/AuthContext.jsx - Product screens → API client: requests data
frontend/src/pages/Search.jsx - API client → API routing: sends requests
- API routing → Authentication: routes auth
backend/routes/authRoutes.js - API routing → Posts and comments: routes posts
backend/routes/postRoutes.js - API routing → Communities: routes communities
backend/routes/communityRoutes.js - API routing → Profiles and follows: routes profiles
backend/routes/userRoutes.js - API routing → Game discovery: routes games
- API routing → Global search: routes search
- API routing → Achievements: routes achievements
- Posts and comments → Feed shaping: decorates posts
backend/controllers/postController.js - Posts and comments → Progression: records activity
backend/controllers/postController.js - Posts and comments → Notifications: notifies actors
backend/controllers/postController.js - Communities → Feed shaping: uses feed helpers
backend/controllers/communityController.js - Communities → Progression: records activity
backend/controllers/communityController.js - Profiles and follows → Feed shaping: decorates posts
backend/controllers/userController.js - Profiles and follows → Progression: records activity
backend/controllers/userController.js - Progression → Notifications: announces unlocks
backend/services/progressionService.js - Authentication → Domain models: reads accounts
- Posts and comments → Domain models: reads and writes
backend/controllers/postController.js - Communities → Domain models: reads and writes
backend/controllers/communityController.js - Profiles and follows → Domain models: reads and writes
backend/controllers/userController.js - Game discovery → Domain models: reads catalogue
backend/controllers/gameController.js - Global search → Domain models: searches records
- Achievements → Domain models: reads unlocks
- Feed shaping → Domain models: queries relations
backend/services/feedService.js - Progression → Domain models: updates progress
backend/services/progressionService.js - Notifications → Domain models: stores alerts
backend/services/notificationService.js - Domain models → MongoDB: persists data
README.md