pedro*
@pedrovearta
Followers
251
Following
2K
Statuses
229
building tools that help companies make sense of their data, sharing what I learn along the journey
Brazil
Joined January 2024
@gonzague Yeah, in my experience, emails are always a pain to configure and to maintain, it's a luxury for larger companies to have
1
0
0
@Nicolas_Silvy I've turned the edge functions into API routes in my Next.js project. The crons I've put in Inngest and the operations that weren't necessarily atomic I've put on my server actions calling the DB using the js sdk.
0
0
1
I usually use either Supabase's auth templates and customize them there (but not on Local Dev) or I connect a product like Resend for these transactional emails But tbh, in my last product, I left only Google OAuth as the login option, it significantly lowered the amount of parts to handle such as transactional emails, password recovery... What are you struggling with?
1
0
0
@iamhtml @NickGatzoulis @appwrite They do but serving them only renders logs in the terminal, I rather have more granular control (time, codes) to be able to understand better
0
0
0
I am still figuring it out tbh, but I am trying to go for an approach like With Supabase: - Auth - DB - RLS logic - RPC for operations that are strictly atomic - Javascript SDK In my backend: - CRUD operations - API routes and functions - File Storage And I use some other services for queues and for crons
1
0
1