How omarg4/ezpc2 works
EzPc is a PC-build recommendation app: users choose a budget and performance priority, receive a parts list, and can save or manage builds when signed in. Its backend selects catalog parts from PostgreSQL; a separate update endpoint refreshes that catalog from an external parts-data scraper. The graph follows the evidenced UI-to-API flow and server-owned calls. The README is empty, so capabilities are based on the sampled source; unsampled login and signup implementations are shown without inferred internals.
Main entry points: App.jsx App routes · firebaseconfig.js Firebase services · Home.jsx Budget and priority · scrape-cron.js Catalog scraper
Components 17
Build recommendation
- Budget and priority
client/src/pages/Home.jsx - Recommended build
client/src/pages/RecommendedBuild.jsx - Loading indicator
client/src/components/Loading.jsx
Catalog backend
- Parts endpoint
server/index.js - Part selection
server/suggestedData.js - Parts catalog
server/db.js - Catalog update endpoint
server/index.js - Catalog scraper
server/scrape-cron.js
Identity and builds
- Saved build history
client/src/components/PreviousBuilds.jsx - Firebase services
client/firebaseconfig.js - Signed-in user state
client/src/components/UserContext.jsx - Login and signup
client/src/pages
Application shell
- App routes
client/src/App.jsx - Header and logout
client/src/components/Header.jsx - Footer
client/src/components/Footer.jsx
Other components
- PC builder
- Parts data source
Connections 20
- PC builder → App routes: opens app
client/src/App.jsx - App routes → Budget and priority: routes to
client/src/App.jsx - App routes → Recommended build: routes to
client/src/App.jsx - App routes → Saved build history: routes to
client/src/App.jsx - App routes → Signed-in user state: provides user state
client/src/App.jsx - App routes → Header and logout: renders
client/src/App.jsx - App routes → Footer: renders
client/src/App.jsx - App routes → Login and signup: routes to
client/src/App.jsx - Budget and priority → Parts endpoint: posts budget allocations
client/src/pages/Home.jsx - Parts endpoint → Part selection: calls
server/index.js - Part selection → Parts catalog: queries parts
server/suggestedData.js - Budget and priority → Loading indicator: shows while waiting
client/src/pages/Home.jsx - Recommended build → Firebase services: reads and saves builds
client/src/pages/RecommendedBuild.jsx - Saved build history → Firebase services: reads and deletes builds
client/src/components/PreviousBuilds.jsx - Signed-in user state → Firebase services: observes authentication
client/src/components/UserContext.jsx - Header and logout → Signed-in user state: reads user state
client/src/components/Header.jsx - Header and logout → Firebase services: signs out
client/src/components/Header.jsx - Catalog update endpoint → Catalog scraper: calls
server/index.js - Catalog scraper → Parts data source: fetches catalog data
server/scrape-cron.js - Catalog scraper → Parts catalog: replaces catalog rows
server/scrape-cron.js