nextjs-subscription-payments

Supabase I set up an authentication with, it was pretty straightforward. I was following this: https://github.com/vercel/nextjs-subscription-payments?tab=r... Do you have suggestions for once users are logged in, for them to be able to submit a selection? The most complicated use case is, each user can purchase multiple entries to a fantasy football contest. And then each week, each user should be able to submit their pick for each entry. The players available for selection each week differ per entry. The most basic use case is, users login and get authenticated, and then on the Account page (which is included in the above linked repo), users can submit their picks manually, through like a Google Form.

Supabase I set up an authentication with, it was pretty straightforward. I was following this: https://github.com/vercel/nextjs-subscription-payments?tab=r... Do you have suggestions for once users are logged in, for them to be able to submit a selection? The most complicated use case is, each user can purchase multiple entries to a fantasy football contest. And then each week, each user should be able to submit their pick for each entry. The players available for selection each week differ per entry. The most basic use case is, users login and get authenticated, and then on the Account page (which is included in the above linked repo), users can submit their picks manually, through like a Google Form.

I use this as a subscription Stripe starter: https://github.com/vercel/nextjs-subscription-payments/tree/... Still quite a bit of customisation to do, but was a good starter.

> Next pushes towards serverless functions and API routes that I didn't really enjoy using for more than just a trivial endpoint. By default (through `next start`) Next.js uses a Node.js server. You don't need to use Next.js serverless: https://nextjs.org/docs/deployment#self-hosting Most large applications don't use API Routes for large workloads. These teams likely have a completely separate backend/API, and Next.js is the connecting piece for their frontend. For smaller teams, or solo devs, it's more common to see their entire backend built with API Routes (most commonly used with something like Prisma): https://github.com/vercel/nextjs-subscription-payments

Just a reminder, it's very similar to: https://github.com/vercel/nextjs-subscription-payments ( he mentioned it in the Readme too)

Related, free template: https://github.com/vercel/nextjs-subscription-payments

a few to get you started: - https://github.com/vercel/nextjs-subscription-payments - https://bedrock.mxstbr.com/