How sridath07/campuslostandfound works
Campus Lost-and-Found provides two user-facing routes: a standalone browser board backed directly by Supabase, and a Java console/optional local HTTP server backed by PostgreSQL. Both support reporting, browsing/search, matching, and claim/return lifecycle work; the Java service owns report rules while its repository loads and saves snapshots. The README documents shared database behavior and protected public access. The sampled source confirms the main Java calls and browser REST requests; the broader page interactions and server routes are only partially excerpted.
Main entry points: LostAndFoundService.java Report service · Main.java Application entry · WebServer.java HTTP server · ReportRepository.java Report repository
Components 18
Browser Website
- Standalone page
website/index.html - Browser workflows
website/app.js - Supabase config
website/supabase-config.js - Served page
src/main/resources/web/index.html - Embedded workflows
src/main/resources/web/app.js
Java Application
- Application entry
src/main/java/edu/campus/lostfound/Main.java - HTTP server
src/main/java/edu/campus/lostfound/WebServer.java
Report Domain
- Report service
src/main/java/edu/campus/lostfound/LostAndFoundService.java - Report lifecycle
src/main/java/edu/campus/lostfound/ItemReport.java - Lost report
src/main/java/edu/campus/lostfound/LostItemReport.java - Found report
src/main/java/edu/campus/lostfound/FoundItemReport.java - Reporter details
src/main/java/edu/campus/lostfound/User.java - Status and type
src/main/java/edu/campus/lostfound/ItemStatus.java
Persistence
- Report repository
src/main/java/edu/campus/lostfound/ReportRepository.java - Access policies
supabase/schema.sql - Supabase PostgreSQL
Other components
- Campus user
- Console user
Connections 22
- Campus user → Standalone page: opens
README.md - Standalone page → Browser workflows: loads
README.md - Browser workflows → Supabase config: uses settings
website/app.js - Browser workflows → Supabase PostgreSQL: reads and writes
website/app.js - Access policies → Supabase PostgreSQL: defines access
README.md - Campus user → Application entry: uses console
README.md - Application entry → Report service: dispatches actions
src/main/java/edu/campus/lostfound/Main.java - Application entry → Report repository: loads and saves
src/main/java/edu/campus/lostfound/Main.java - Application entry → HTTP server: starts optional server
src/main/java/edu/campus/lostfound/Main.java - HTTP server → Report service: handles report actions
src/main/java/edu/campus/lostfound/WebServer.java - HTTP server → Report repository: saves updates
src/main/java/edu/campus/lostfound/WebServer.java - HTTP server → Served page: serves assets
src/main/java/edu/campus/lostfound/WebServer.java - Served page → Embedded workflows: loads
- Report service → Lost report: creates
src/main/java/edu/campus/lostfound/LostAndFoundService.java - Report service → Found report: creates
src/main/java/edu/campus/lostfound/LostAndFoundService.java - Lost report → Report lifecycle: extends
src/main/java/edu/campus/lostfound/LostItemReport.java - Found report → Report lifecycle: extends
src/main/java/edu/campus/lostfound/FoundItemReport.java - Report lifecycle → Reporter details: contains
src/main/java/edu/campus/lostfound/ItemReport.java - Report service → Report lifecycle: searches and updates
src/main/java/edu/campus/lostfound/LostAndFoundService.java - Report service → Status and type: checks lifecycle
src/main/java/edu/campus/lostfound/LostAndFoundService.java - Report repository → Supabase PostgreSQL: loads and saves
README.md - Report repository → Report service: restores reports
src/main/java/edu/campus/lostfound/ReportRepository.java