How to set up Payload with Supabase

[@SiBtoday]

I just wanted to point out, that this tutorial was just perfectly recorded. Learned a lot, as someone who just got across Payload :) Keep up, that amazing work!

[@00titanium00]

Maybe it's possible to adapt fro selfhosted supabase because from docs seem that actually it can be and issue connecting to the supabase bucket ...

[@longtranminh1545]

I stuck with "unhandledRejection Error [ERR_REQUIRE_ESM]: require() of ES Module ... ode_modules\@payloadcms\storage-s3\dist\index.js from ...\src\payload\payload.config.ts not supported. Instead change the require of index.js in...\src\payload\payload.config.ts to a dynamic import() which is available in all CommonJS modules. My source is "npx create payloadcms" but i can't use s3Storage, please hepl me pls!

[@madusara.liyanage]

I have a mongodb connected to a payload app and whatever the images I upload to payload (under 'media' collection) gets broken after some time. Now I connected a supabase s3 bucket to the project, it gets uploaded to supabase (and mongodb both) and still the image file gets broken after a while giving a 500 error in the get request. But the image resides properly inside the bucket when checked from supabase side. Do you have any clue why? TIA

[@chrisarrow]

At 12:36 how do you go about disabling payload access control?

[@DarkLide92]

Is it recommended to use supabase cli to do the migrations? Or should we stick with payload doing migrations?

[@erdemarslan3371]

How can I use multiple buckets?

[@Amitsarker]

Great tutorial! Thanks for sharing your expertise. Keep up the fantastic work!

[@osamaalnaggar]

Can we use supabase Authentication with Payload? We need users to sign in through Google and Payload currently doesn't offer that

[@payloadcms]

You can determine your own auth strategy (payloadcms.com/docs/authentication/config#strategies). Otherwise, Payload does offer an SSO plugin (available on enterprise plans) that is more robust and includes Google.

[@danielstill5625]

Agreed. It's nice that Payload does auth, but Supabase specialises in auth, so it would be so nice to use Supabase for auth.

[@chongjumai2905]

With the latest beta63. I am not able to create the first user. It always say invalid password with using the online Supabase. But if I changed the connection string to local dev, it works.

[@JohnBuildWebsites]

I keep getting `ERROR: InvalidAccessKeyId: The Access Key Id you provided does not exist in our records.` despite repeated attempts to replace and copy/paste a fresh one. Any ideas?

[@TomKendry]

I ran into a lot of trouble attempting to get through the storage portion of this guide as it seems that the methods have changed in the past 11 days since this video was posted. I had to install @payloadcms/plugin-cloud-storage and I followed the guide on the readme for setting up the plugin which is considerably different than the approach outlined here. I also had to be sure to include an "endpoint" field in my s3 adapter config. I was a little shocked to see that this guide and the written counterpart were posted under 2 weeks ago and seem to be completely outdated and confusing for new users.

[@georgekrax]

Could I use something like Payload + Supabase + Prisma?

[@ricozuares]

What about AppWriter?

[@varmahacks3150]

Payload 3.0 cms deploy In vercel video Is it possible to deploy the payload in local setup server/ custom server

[@payloadcms]

You can deploy Payload anywhere Next.js can be deployed-which is pretty much anywhere. You can also run Payload anywhere you can run node, including on your local machine.

[@developer-tq9kj]

what about convex database? can we use convex with payload?

[@developer-tq9kj]

what about convex? can we use convex with payload?

[@minggux1694]

Awesome, very helpful for a quick project.

[@watchbro3319]

that so nice man thanks does pocket base work as well

[@_Wild_Wanderlust_]

Thank you for this tutorial payload, I followed every step till I got to the storage-s3 part. After setting the legacy peer deps to true, I get the following error message. Wonder if you could help. Thank you very much in advance. Error: Mismatching payload dependency versions found: payload@3.0.0-beta.90, @payloadcms/plugin-cloud-storage@3.0.0-beta.29. All payload and @payloadcms/* packages must have the same version. This is an error with your set-up, caused by you, not a bug in payload. Please go to your package.json and ensure all payload and @payloadcms/* packages have the same version. Following are the dependencies: "dependencies": { "@payloadcms/db-postgres": "beta", "@payloadcms/next": "beta", "@payloadcms/plugin-cloud": "beta", "@payloadcms/richtext-lexical": "beta", "@payloadcms/storage-s3": "^3.0.0-beta.29", "cross-env": "^7.0.3", "graphql": "^16.8.1", "next": "15.0.0-canary.104", "payload": "beta", "react": "19.0.0-rc-06d0b89e-20240801", "react-dom": "19.0.0-rc-06d0b89e-20240801", "sharp": "0.32.6" },

[@thezeppo]

You need to install the storage version that matches the payload beta version, so in your case you have "payload@3.0.0-beta.90" so install storage-s3@3.0.0-beta.90 You'll probably have a high vulnerability, if you audit fix it'll change the version so don't do that. I found this out the hard way :) Obviously (hopefully?) when out of beta these won't be issues

[@peterkyle01]

This is amazing,I have been looking for a way to do this then came this video.Thanks again for this 😃

[@muperdev]

Another masterpiece I guess!

[@JohnVandivier]

brilliant

[@Nin_Cada]

Release the stable version already!!😐

[@SiBtoday]

Any ETA for this already? :)

[@coherentpanda7115]

They can't release until NextJS 19 is released, as they are reworking Payload to be better compatible with the latest version of React and new NextJS features. Since both React and NextJS are not ready with the latest stable releases, Payload won't be releasing until after.

[@BruceWayne-s4m]

is anyone having this issue with conflicting beta packages? Internal error: Error: Mismatching payload dependency versions found: @payloadcms/richtext-lexical@3.0.0-beta.77, @payloadcms/plugin-cloud-storage@3.0.0-beta.29. All payload and @payloadcms/* packages must have the same version. This is an error with your set-up, caused by you, not a bug in payload. Please go to your package.json and ensure all payload and @payloadcms/* packages have the same version. I did create a .npmrc file settings legacy-peer-deps=true but that didnt help unfortunately

[@JohnBuildWebsites]

I had to manually set all the beta versions to the same to get it to work. By default some beta versions installed are very out of date.

[@Michael-Martell]

Can you do an integration with Xata.db?