examples VS developer-portal

Is anyone aware of a way to make a direct connection to Postgres with transaction support on Vercel Edge functions? The 'pg' package doesn't work on edge for me. The obvious answer would be @vercel/postgres but I find their lack of documentation rough and for whatever reason I can't get it to connect on my local computer using the Supabase-provided local database connection string. This is apparently a known issue (https://github.com/vercel/storage/issues/123, https://github.com/vercel/examples/issues/701) where in order to make this (or neon's package) work you need a WebSocket proxy? Is a direct Postgres connection from edge just impossible right now? Or do others have it working somehow?

I have cloned this repo: https://github.com/vercel/examples/tree/main/python/nextjs-flask. I am using the repo to make an api call from the front end to the back end. when running fetch("/api") I get an error with status 500, why is that?

Demo: Alt Text Generator GitHub: Alt Text Generator Repository

I copied the Template that they provide for the testing, you can get the template source on GitHub. I modified its page.tsx file just to set and get a value from the database.

Take a look at this example: https://github.com/vercel/examples/tree/main/solutions/subdomain-auth

So AFAIK now with Vercel Postgres is possible to have connection pooling using prisma out of the box, this means that no more bottlenecks with lots of clients connected to the web app right? Source: https://github.com/vercel/examples/blob/main/storage/postgres-prisma/prisma/schema.prisma

I have a server component that reads a database table in this new way (Vercel Next JS Postgres Example). I also have a client component that updates that calls a fetch to update the same table. How can I ensure that the data in my server component doesn't grow stale?

Additionally, Redis can be used in combination with Vercel Edge cache using: https://github.com/vercel/examples/tree/main/edge-api-routes/cache-control

Hostname rewrites example

Hello everyone! Time for another rollup of all the changes that have been happening on the Sitecore Developer Portal since our last update in April. This quarter focused on how we can get more enablement content out for developers, and lay the ground work for the new XM Cloud product.

As a leader for Developer Relations, I wanted to see if this was true for our developer audience as well, so I looked at the data for the Developer Portal. The distribution was really similar, though with some minor differences in percentages. Southern Asia sits at 22% instead of 23% and the European subcontinents now add up to 28%. All in all, though, it seems our developer audience distribution matches pretty well with our community forums distribution.

Do you have an idea? We welcome feedback and suggestions in our GitHub repo: https://github.com/Sitecore/developer-portal