How ruboma/social-network-git works
Project type and purpose
• This is a full-stack social networking application.
• Frontend: Next.js app providing pages for feed, profiles, groups, chats, etc.
• Backend: Go-based REST + WebSocket API server handling authentication, feed generation, posts, comments, chat, groups, notifications, and sessions.
• Database: Relational store (migrations present) for users, posts, comments, groups, followers, sessions, notifications, messages.
• File storage: Local “uploads” folders for images (profile, post, comment).
• Orchestrated via Docker Compose with separate containers for frontend, backend, and (implied) database.
File structure
• Top-level directories “frontend” and “backend” encapsulate the two main components.
• backend/app contains HTTP handlers grouped by feature (chat, feed, posts, users, etc.).
• backend/server implements server bootstrapping and WebSocket entry point.
• backend/database holds DB connection, CRUD logic, and SQL migrations.
• frontend/app follows Next.js 13 “app” directory with page.js routes and component structure under components, context, group, etc.
• docker-compose.yml and start.sh orchestrate services.
README for additional insights
• Frontend: Next.js, tailwind, uses create-next-app blueprint, listens on port 3000.
• Backend: Simple “go run .” startup; implicitly listens on a port (e.g., 8080).
• No mention of external third-party services—purely local Docker network.
Elements
• Green for UI components (Browser & Next.js)
• Blue for API/backend (Go service)
• Orange for data/storage (DB & file system)
• Inside DB, annotate tables or migration sets (Users, Posts, Comments, Followers, Groups, Requests, Notifications, Sessions, Messages)