All activity
Satish Pophaleleft a comment
To kick things off for me, the worst part was always dealing with Applicant Tracking Systems (ATS). You can have a visually stunning resume, but if the PDF renderer flattens the text into vector graphics, the ATS reads it as a blank page. Figuring out how to use Typst and WebAssembly to fix that natively in the browser was the hardest, but most rewarding, part of building this!
Building a resume shouldn’t cost $15. Here is how we are fixing it. 🛠️
Satish PophaleJoin the discussion
Satish Pophalestarted a discussion
Building a resume shouldn’t cost $15. Here is how we are fixing it. 🛠️
Hey Product Hunt! 👋 I'm Satish, a software engineer, and I'm gearing up to launch Infinite Resume here on April 8th. Over the last few years, I've watched brilliant people spend hours crafting the perfect resume, only to get hit with a surprise paywall at the very end just to download their own PDF. Even worse, those generated PDFs often fail Applicant Tracking System (ATS) parsers entirely. I...
Satish Pophaleleft a comment
We keep it simple with per-environment .env files and a validation script that runs pre-deploy to ensure all required Supabase vars (SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY) are present and non-empty. For production, secrets live in the hosting provider's env config, never in checked-in files. Key rotation is manual but infrequent the validation step catches misses before...
How are you managing Supabase credentials across environments without things drifting?
Eric Della CasaJoin the discussion