How rahulr324/medfinder works
MedFinder lets users search for medicines by name and locality, then returns matching pharmacies with prices and store details. The backend also exposes a common-medicines catalog and initializes MongoDB from sample data. The README describes price comparison and store-location features; the sampled backend returns price and location fields, but the HTML files were not sampled, so frontend-to-API wiring is unverified.
Main entry points: nodejs-backend.js Pharmacy search · search.html Search page · results-html.html Results view · sample.json Sample pharmacy data
Components 12
Web interface
- Search page
search.html - Results view
results-html.html - Application page
index.html
Search backend
- HTTP server
nodejs-backend.js - Pharmacy search
nodejs-backend.js - Common medicines API
nodejs-backend.js - Data initializer
nodejs-backend.js
Medicine data
- Sample pharmacy data
sample.json - Pharmacy records
- Common medicine list
Other components
- Medicine seeker
- MongoDB Atlas
Connections 11
- Medicine seeker → Search page: searches in
README.md - Search page → Pharmacy search: submits query
- Pharmacy search → Pharmacy records: queries stores
nodejs-backend.js - Pharmacy search → Results view: returns matches
- HTTP server → Pharmacy search: routes requests
nodejs-backend.js - HTTP server → Common medicines API: routes requests
nodejs-backend.js - Common medicines API → Common medicine list: reads list
nodejs-backend.js - Data initializer → Sample pharmacy data: reads records
nodejs-backend.js - Data initializer → Pharmacy records: seeds stores
nodejs-backend.js - Data initializer → Common medicine list: seeds medicines
nodejs-backend.js - HTTP server → MongoDB Atlas: connects to
nodejs-backend.js