How salint/social-media works
Project type and purpose
• This is a full-stack social media web application built with Node.js/Express and server-side rendering (EJS).
• The purpose is to allow users to sign up, log in, view profiles, create/edit posts, and manage sessions.
File structure
• Top-level files: package.json (Node dependencies), database.sql (schema), .env (config).
• src/ folder follows an MVC-style breakdown:
• controllers/ – request handlers (auth, user, post, root)
• services/ – business logic & external interactions (database, session, server, post, user)
• middleware/ – request pre-processing (auth)
• util/ – shared utilities (custom error class)
• main.js & index.js – app bootstrap and HTTP server startup
• static/ – public CSS assets
• views/ – EJS templates for each page (login, signup, profile, posts, 404, etc.)
README for additional insights
• Express.js server
• EJS for server-side HTML rendering
• SQL (via database.sql) as the data store
• Session management (likely via cookies)
a. Main components
1) Client (Browser + static assets + rendered EJS pages)
2) Web Server (Express app)
3) Controllers (auth, user, post, root)
4) Services (database, session, user, post, server)
5) Database (SQL)
6) Middleware (auth)
7) Util layer (ErrorEx)
b. Relationships & interactions
• Browser sends HTTP requests → Express Server
• Server applies auth.middleware → routes to appropriate controller
• Controller invokes service(s) for business logic
• Service uses database.service or session.service to read/write data
• Controller renders a view via EJS or redirects/responses
• Response returns HTML/CSS for the Browser
c. Architectural patterns & principles
• MVC-style separation:
• Model = database + database.service
• View = EJS templates + static assets
• Controller = controllers folder
• Service layer abstracts data and session logic
• Middleware handles cross-cutting concerns (authentication)
• Single monolithic codebase
d. Key technologies/frameworks
• Node.js & Express.js (server)
• EJS (templating engine)
• SQL database (schema in database.sql)
• Session handling (session.service + cookies)