How deepakpokhrel1/local-services works
Project Type and Purpose
• This is a full-stack web application called “Local Services Directory.”
• Frontend: React.js SPA with Redux and Tailwind CSS for UI/UX.
• Backend: Node.js + Express.js monolith implementing REST APIs.
• Database: PostgreSQL (accessed via Prisma ORM or Sequelize).
• External services: Google Maps API for geolocation, Stripe for payments, email (SMTP/Nodemailer), SMS, Sentry for error tracking.
File Structure Analysis
• Top level:
• backend/ – Express server, routes, controllers, services, models, migrations, seeders, middleware, configuration, logs.
• frontend/ – React app: public assets, src/components, pages, styles, mock data, proxy setup.
• nginx/ – reverse-proxy config.
• docker-compose.yml & Dockerfile – container definitions.
• crontab.txt – scheduled jobs (database backups).
• Backend follows MVC-style:
• routes → controllers → services → models (ORM)
• middleware layer for auth, CORS, rate limiting, error handling.
• migrations/seeders for schema and dummy data.
• Frontend organizes by feature:
• components (UI + domain), pages (routes), API modules (axios wrappers), contexts.
README Insights
• The stack summary and environment setup clarify external dependencies and runtime pieces.