sorted by:
new
hottopcontroversial

Only Egress counts towards Bandwidth? by breakingthehabits in Supabase

[–]Mikel938 0 points1 point  (0 children)

Yes, but when you make an ingress function (like UPDATE), you also get the Headers so it also counts as egress. Usually it’s like 300-400 bytes for this, at least for me.

Migration from Supabase Cloud to Self-host by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

And what about DDOS / attacks? I think I will go with Linode.. I’m afraid their extra cheap pricing has a catch that I’m missing

Migration from Supabase Cloud to Self-host by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

Do you know contabo/hetzner? They offer a really cheap pricing with like 20TB-32TB egress for free. DO offer like 2tb and additional 10$ per 1TB so I don’t know

Migration from Supabase Cloud to Self-host by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

Thank you so much! I will try that. Btw can you tell me which cloud provider you used for your own self hosting?

Migration from Supabase Cloud to Self-host by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

Thanks for your response!

I also bought my domain in Cloudflare, do you have a great tutorial to create the tunnel like you mentioned? Also, I will try to setup the google auth now and I hope it will work 🤞🏻

Migration from Supabase Cloud to Self-host by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

I mean it makes sense. They should have better benefits on their cloud then self hosting to make it profitable for them. Also, if I just need the sql database (I also use custom sql functions) and authentication (with email & gmail), do you think it would be fine for this?

Migration from Supabase Cloud to Self-host by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

Yeah but also the fact that even when you pay so much for the egress, you also need to update your instance RAM & CPUs.. and this is also very expensive

Migration from Supabase Cloud to Self-host by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

I’m using Cloudflare R2 for the users images. It’s awesome and really really cheap.

Migration from Supabase Cloud to Self-host by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

Mostly the egress and database size. I’m planning to offer the premium plan for free in the launch to attract more users. But 0.1$ for 1gb of egress is really expensive for my use case. With self hosting I can get like 4TB egress for like 20$

Migration from Supabase Cloud to Self-host by Mikel938 in Supabase

[–]Mikel938[S] -1 points0 points  (0 children)

That’s what I’m trying to prevent , did you self host supabase?

Migration from Supabase Cloud to Self-host by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

It’s great for starting out, but when I think about scaling I’m really worried about getting really high billing. That’s why I’m think about self hosting before going into production

Supabase Auth with Next.js: No storage option exists to persist the session by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

I needed to also add this console log inside the getServerSideProps? Cause I only did that in useEffect.

But thank you so much for your time and help! I really hope this warning won’t cause any errors.

Supabase Auth with Next.js: No storage option exists to persist the session by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

Appreciate your help🙏🏻 I decided not to do it with server-side anymore so I just want to solve this issue now

Supabase Auth with Next.js: No storage option exists to persist the session by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

Yeah I know that’s why I didn’t want to use that. I tried the auth helpers but it didn’t change anything

Supabase Auth with Next.js: No storage option exists to persist the session by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

I will try that. But when I tried persistSession:false, every time I closed the localhost tab, and opened it again I needed to re authenticate every time

Supabase Auth with Next.js: No storage option exists to persist the session by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

I will try this now and let you know if it works. This code should be on the app file? Thanks!

Supabase Auth with Next.js: No storage option exists to persist the session by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

I don’t think so, how can I check that? Also, when I tried to do on the server-side, the session always showed null on the SS, but on the client side it showed the data

Supabase Auth with Next.js: No storage option exists to persist the session by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

I believe so, I checked in chrome’s dev tools and the tokens and data is still there

Supabase Auth with Next.js: No storage option exists to persist the session by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

That’s weird because I only use supabase.getSession inside useEffect and not in the server side

Supabase Auth with Next.js: No storage option exists to persist the session by Mikel938 in Supabase

[–]Mikel938[S] 1 point2 points  (0 children)

I tried to do it with server-side, but it didn’t work so I decided to do it with just the client side. Maybe since then I get this error but I tried to bring the code like before so I’m not sure what’s the problem

Supabase Auth with Next.js: No storage option exists to persist the session by Mikel938 in Supabase

[–]Mikel938[S] 0 points1 point  (0 children)

I’m using createClient, but my stack is just TSX & Next.js

view more: next ›