How kylaaz/jakarta-park-finder works
Project Type and Purpose
• Full-stack web application called “Jakarta Park Finder.”
• React-based single-page application (SPA) frontend for end-users and administrators.
• Node.js/Express REST API backend exposing endpoints for parks, damage reports, users, reviews.
• MySQL relational database for persisting parks, users, reports, reviews.
• File storage for uploaded damage photos (under /backend/public/uploads).
• Integrates with Leaflet (map/tile service) to render park locations.
File Structure Analysis
• Top level: two directories, /frontend and /backend, each with its own package.json and docs.
• Backend follows MVC-ish layout:
• src/models (data schemas),
• src/controllers (business logic),
• src/routes (API routing),
• src/middleware (auth, roles, errors),
• src/config/database.js (MySQL connection),
• src/utils/jwt.js (JWT handling),
• public/uploads (static file hosting).
• Frontend uses React + Vite:
• src/pages & src/view/pages (page components),
• src/components (reusable UI pieces: auth, park cards, forms),
• src/admin (admin-only routes and layouts),
• src/services (Axios API wrappers),
• src/context/AuthContext.jsx (JWT token & user state),
• index.html → main.jsx → App.jsx → routed via React Router.
Key Insights from README
• Features: park discovery, search, damage reporting, admin dashboard, reviews.
• Tech stack: React/Vite/Tailwind, Node/Express, MySQL, JWT, CORS, Express-fileupload.
• Deployment: Heroku for both backend and frontend.
• Environment variables: API URL, database creds, JWT secret.