How progettotecweb/squealer works
Project Type and Purpose
• This is a monorepo hosting a full-stack social-media platform (“Squealer”) plus two admin dashboards:
• SquealerApp: a user-facing Next.js (React) application
• Squealer SMM Dashboard: a Vue.js analytics/marketing dashboard
• Squealer Moderator Dashboard: a pure-JS moderator interface
• It also contains:
• A Node.js/Express backend (under server/) exposing REST routes for users, channels, notifications, subscriptions, etc.
• A MongoDB access layer (under db/), with JS wrappers and JSON fixtures.
• Utility scripts (bots, AI pipeline, Python startup script), static assets, Docker and Nginx configs.
File Structure
• Top-level directories separate concerns:
• SquealerApp/ (Next.js) – React pages & API routes, custom hooks, components, styling, authentication.
• SquealerSMMDashboard/ (Vue/Vite) – SMM analytics for social media managers.
• SquealerModeratorDashboard/ – static HTML/JS for moderators.
• server/ – Express server with routers: usersRouter.js, channelsRouter.js, squealsRouter.js, subscriptionRouter.js, plus notifications/.
• db/ – Mongo connection and data access logic; JSON backups/fixtures.
• bots/ & AI/ – automation scripts and AI pipeline module.
• nginx/ – reverse-proxy config.
• docker-compose.yaml – container definitions (frontend, backend, MongoDB, nginx, etc.).
README Insights
• Confirms three front-end apps built with different stacks (React/Vue/js).