GiggleGigs is a job board I run: Django + DRF on the backend, React + Vite on the front (on Vercel), Celery for background work, and PayPal for payments, all on a single 2 GB DigitalOcean droplet. Companies post gigs, seekers apply, and companies pay to unlock contact details and post more jobs.
In the last post I got deploys down to zero downtime. This one is about what those deploys were shipping.
Why I looked
I watched a Facebook reel about checking RLS (row-level security) on websites. RLS is a database feature that decides which rows each user can read or change. It's mostly a Supabase thing, where the browser talks to the database directly, so a missing policy means anyone can read the table.
GiggleGigs doesn't use RLS. Django sits between the browser and Postgres, and the API code decides who sees what. But that only moves the question, it doesn't answer it.…