Software engineering intern: React + Supabase school platform with PostgreSQL Row-Level Security, Edge Functions for auth and privileged ops, and GitHub Actions tests before every deploy. Public surfaces: safapp.org and arshad.guide.
- Stack
- TypeScriptReactSupabasePostgreSQLViteGitHub Actions
- Outcomes
250+
Active users
19
Edge Functions
937
CI tests
- Highlights
- Live in production for a Michigan school (250+ users)
- 19 Supabase Edge Functions (auth, admissions, Stripe kiosk, push, prayer sync)
- 937 Vitest tests gating GitHub Actions deploys
Gallery
Problem and outcome
The school needed grades, records, and administration offline from spreadsheets, with five access levels that must not see the same rows. The platform is live in production for 250+ users. Authenticated admin rows stay private; public surfaces are safapp.org and arshad.guide.
Role
- Employer: Darul Uloom Michigan (Warren, MI)
- Product: Arshad on the SAF platform
- Role: Software engineering intern (May 2026 – present)
- Owned: Postgres schema + RLS, Edge Functions, role-differentiated React UI, GitHub Actions CI
Architecture
React (Vite) — five role-differentiated UIs
│
▼
19 Edge Functions — auth, admissions, Stripe kiosk, push, prayer sync
│
▼
PostgreSQL (53 tables, 133 RLS policies in schema.sql)
GitHub Actions verify — 937 Vitest tests gate every deploy
Technical decisions
1. Enforce access in the database. 133 RLS policies (schema.sql) so a missing UI check cannot casually leak another role's rows.
2. Privileged ops in Edge Functions. 19 functions keep auth and sensitive writes off the client.
3. Block deploys with tests. 937 Vitest tests in the verify job
(npm run test in saf-web/) before ship — same gate as typecheck, lint,
production build, and secret scan.
Validation
Production use by 250+ people across five access levels; CI required green (937/937) before deploy.
Limitations
Gallery shows signed-out Arshad / SAF surfaces. Authenticated grading and
attendance with synthetic demo records are not published here yet — those need
a controlled demo export. Schema counts above are from supabase/schema.sql
(53 tables, 133 policies); live DB may diverge.