Tanner Scadden
Explore posts from serversDTDrizzle Team
•Created by Tanner Scadden on 10/3/2024 in #help
Max connection issues
I am running into max connection issues when I am using supabase within an application hosted in a serverless environment (vercel).
I've done everything I can find by the docs, but if I have a spike of 300+ users on my app at once, I start to run into a lot of max connection errors.
I am using trpc to help batch request and limit connections made. I create the postgres connection outside of drizzle, set max connections to 3, and pass the instance in. I am using transaction mode in supabase so it uses supavisor. I have prepared statements set to false.
Does anyone have any advice that might be harder to come by? I am not as familiar with serverless environments and am about to pull the plug and move it over to a long-standing server to help my app scale.
Went through this guide as well
https://github.com/orgs/supabase/discussions/22305
Thanks!
7 replies
pnpm v8
pnpm v8 has a major version bump for lock.yaml. This is causing any builds to fail where the lock file is generated with pnpm v8. Examples can be found in projectId a2ab11df-7f4e-4ea5-8c53-1f345f0fc425 under staging environment.
3 replies
monorepo .next folder not included in docker image
ProjectId: a2ab11df-7f4e-4ea5-8c53-1f345f0fc425
Using Nixpack and turborepo. Build runs fine, but when it runs the start command it logs out
I can tell it to build on the start command again, but half the time that will run into this error:
50 replies