Prestigious_Park7649

probably good for vibe coders but it would be funny if you built it with vibe codeing xD. see vibe coding is not bad it is bad when your mental modals are not string and you are not writing tests or even if you arent you should always know the best practices your RnD should not be done by any llm

i would go with the landing page first do the seo proper blogs templates pricing pages , not app screen shots but just an i dea and email newsletter or for any further suggestions that might users want to create i do that perallel when building frontend and add pages for feature what have build and what am i currently working and what are the future features (next deployments) a proper visualized versions controlls this helps wheather your products fits what it needs etc i find that useful the rest workflow is the pretty good

so your concern abouting scripting , well there is good new and badnews good news is that some scripts are now allowed in browser and bad news is some are allowed so we yh supbase donst have the ratelimitting context unless you are on free plan so i would use a third party tool only for ratelimmiting a middllware between my client and server , the other option i have is to create an edgefunction (backened for frontend) that validates on jwt and apply ratelimmitng logic if proceed . one thing is for sure what you can compromise is speed over security

ok first question how do user get into a loop walk me through it , avoid that users flow should be streamlined no loops how can he does loop calling by pressing x button againa nd again , well i would suggest to streamline your user action flow never allow user to make an api call in a loop , and set ratelimmiting per user in the context so your app know which calls are exceeding and needs to be stopped

ok for select query rate limiting bro let me itroduce you to a thing called cache , you store your query data in cache so when the data isnit changed or the session is not being comprimised you get cached data instead of making every supbase query call , in react we have library called tenstack query in which data is cashed per its unique it depends on you how you managed but this is where you programming skills

if it was like you think it was then no other big business would use it it would target only small customer based busisness good that you learned and shared

supbase doesnt handle only user queries , i have enabled cronjobs , triggers, edgefunctions (mostly webhooks)

total daily invocations

yh ut supports vector db but so far i heard that for you know fast most optimized way to structure your llms schema is combination of graphql and vector db its more faster and efficent. for now no i dont need document uploads for ai powered apps

two options we have on migration one is to host your project image as in docker as complete instance which doesnt suit me the other one is to replace each and every insttance of supbase with aws , like database , auth , storage, edgefunctions etc this is more robust and scalable and its cheaper than supbase as i heard , cuz you have to do every config by yourself where supbase do if for you , i would first create terraform (which is manual work although we have some splutions in aws like encore that programatically set configs )carefully then proceed to miregration if that ever needed

i think there is a option for mireagting whole project i didn't read that but you should defiintly read it

i have not swtiched one but i am currently using supbase but so far its doing pretty good with 50k daily traffic , it also depends on how you define. if this threshold increase i would switch to aws why cuz we can scale system horizantally as per needed , although supbase also have upfront cdns which cover latency issues , but for now start for begining i would go with supbase

for email signups i added a phone otp then users is authicated , with email only user is created but not autheticated and to access tables for read and right i prefer polices only for authicated users scopes which stops this voilation

you must have missed somethings in auth polices use oauths of gmail ,github and for email enable phone verification then create an account create authpolices and yh captcha is great but now very old use email signups via magic link or otp .

my suggestion was to show mapped url in the npm packages that way i could hide my actual edge function url , so that my projectid of supabase stays remain hidden is it doable ?

i think jwt is an over head if my api key and rate limiting is working properly wdys?

got it thank you sir

Thank you for suggestion i would really love to see your work . may be i can learn more from your work and think of another way . I am really shifting my way of building web apps , and that is to create an mcp for every app that i create it a bit more of a work but now i think its like a compulsory for maximum reach

yh it will be a zoo of models . but my idea is to build one thing at time , we can use combinations of rag and multi quantized models eg. chooseing tech stack and picking up the exact boiler plate . UI / UX design principle (RAG). app folder structuring . Best cache management (web) techniques / hydration. writing tests. like it will give more control over the development. anthropic outperform most of models with tools calls and i have read about it in some article that they create tools/function calls real-time . and I am just mad at RAM manufactures they dont care about B2C now all tech giants has caused shortage

yup count me in

i am facing same issue i want users to sign in / signup users without the password , the already created users with signup() method works well with sing with otp but new users faise an error even with shouldcreateuser flag to true share your solution please i neeed that asap