What PocketBase 0.23 Means For Developers

[@hambaba]

Always excited to see your video about pocketbase! keep them coming! Anyway, do you know how to scale pocketbase horizontally? I heard it's possible using LiteStream or LiteFS, haven't got the time to explore them further tho. Would be great if you can make a video about that!

[@earlymorningdev]

Thanks for the encouragement 🙏 😊 yep definitely will be doing that. It is even more possible now that data base connects are here for 0.23

[@dandogamer]

@hambaba it supports external db providers now so you should be able to hook it up to turso. However pocketbase under the hood uses hooks and from what I last read from the author these arent going to work properly when you start scaling horizontally. Maybe the refactoring in this release also fixed that but I will need to check the notes :)

[@madmaxdev]

Congrats 🎉

[@earlymorningdev]

Thanks man!

[@AsyncDpp]

Astro is the best right now! Keep going!

[@earlymorningdev]

I'm so glad I picked it up. Going to keep going with it. Just need more time to execute on my thousand ideas 💡

[@chrschoeni]

Amazing, thanks for your video

[@dirtbagmoto]

Also very excited to see this version officially released soon ™ Nice walkthrough but I was wondering if there is a way to use OTP as a magic link, if that makes any sense. OTP works if the user is already in the DB but it would be cool if I could also send a link to an email that is not yet registered. Any ideas on how to accomplish this with pocketbase?

[@earlymorningdev]

Hmm I think that sort of behaviour could be built out as a custom hook but my problem with that is I have a feeling that now we have this OTP feature I think that magic links may be coming in the future so there isn't a point for me to build it out

[@jasontruter4981]

By extending with go, you can achieve this. You could create a guest user when they enter their email, when you send the email and they open the otp link, you could set the user as verified once they have clicked the link on their email and then log them in. // simple otp creation otp := core.NewOTP(app) otpPassword := security.RandomStringWithAlphabet(6, "1234567890") otp.SetRecordRef(user.Id) otp.SetCollectionRef(user.Collection().Id) otp.SetPassword(otpPassword)

[@Csepowertrip123]

have you tried payload boss?

[@earlymorningdev]

I have what's your experience of it?

[@steve-adams]

A good example of Next.js too clever for its own good is "use server". I had to dig into that a few weeks ago and good god, there's way too much magic. Your issue with managing state between server and client is something I think only really became a major issue after the app router. It's too easy to create situations with stale state without it being evident why. I think tanstack's framework seems to address this, and there are some really cool ideas coming down the pipes. I'm excited to see what happens there.

[@earlymorningdev]

Yeah I agree. App router is a good idea but the implementation is not well done. It's the opposite of simple which is the gold standard for programmers. I honestly have had a gutful from it but I still will use it cause it's popular. For my side projects I think I'm just moving to Astro

[@earlymorningdev]

As far as tanstack that has been the only way to enjoy next.js but even that is silly. I'm going to check out tanstack start at some stage as there looks to be some awesome stuff happening there

[@hugo-abdou]

I think you should start thinking about code your self and use the ai to help you not to code for you

[@earlymorningdev]

Well said sir, I definitely think about how to code myself. I understand the code that the ai is writing. I have written without ai for a long time. Ai helps to demonstrate really quickly how good pocketbase is

[@dnlmgwi]

Lol "Thats for weak ones", bookmarked