random 502 bad gateway errors with Strapi endpoints - app deployed on Fly.io + postgres database on Supabase

@spiff-radio I’m guessing something similar is probably happening. I’m not very familiar with Supabase, but it’s hard to fundamentally fix problems around here from our side, and I’d recommend the option of continuing to have as few idle connections as possible.

We recently implemented a time-based pool cleanup to address this problem. However, for Strapi I believe that simply setting the minimum to zero is good enough. (We’ve actually been using Strapi recently in a similar situation with everything on Fly.)