PocketBase

This Twitter/X account no longer will be actively used and will be deleted in the near future. For security and new releases notifications you can subscribe to the GitHub repo's > Watch > Custom > "Security alerts" and "Releases" events.

v0.25.0 Release - github.com/pocketbase/poc… This is mostly a maintenance release with some long overdue dependencies and Google OAuth2 APIs upgrade, new Trakt OAuth2 provider, optional case-insensitive identity+password login and other minor fixes.

v0.24.0 Release - github.com/pocketbase/poc… Happy new year! This release comes with minor Create API rule breaking change that also as a side effect improved slightly the create API performance, option to trigger the registered cron jobs from the UI, and other minor improvements.

v0.23.0 Release - github.com/pocketbase/poc… This is a major refactoring and introduces a lot of changes - new (and hopefully simpler) Go/JS APIs, new hooks allowing better control over the execution chain, batch Web API, OTP and MFA support, builtin rate limiter and many more.

Instagram OAuth2 provider deprecation - github.com/pocketbase/poc…

@brainage19 Additionally, if your PocketBase app is deployed on production, note that some VPS providers may block outgoing mail ports like 25, 465, 587, etc. as a basic abuse protection and you may have to contact them.

@brainage19 You can rule out PocketBase issue by testing with a different SMTP provider like mailtrap.io or smtpbucket.com. For Gmail see also github.com/pocketbase/poc…. In all cases, I don't recommend entering your SMTP credentials in random online forms.

Does anyone have experience with @pocketbase email verification? I've been going insane the last 2 days trying to debug this. Pretty sure it's PocketBase at fault because my settings work with free SMTP testing services.

@dahjson You were banned because you spammed the issues tracker, discussion and the support mail and this type of behavior is not OK. You didn't "asked questions" and just wrote that "OAuth2 should be implemented this way" and I answered several times why we don't do that. Please move on.

@pocketbase Careful using this with your project. Creator banned me from the GitHub repo just for asking questions about OAuth. Not recommended for anyone with a serious project.

JS SSR - issues and recommendations when interacting with PocketBase: github.com/pocketbase/poc…

@ajmalmohad_ Side-note: Be aware that the current Go frameworks APIs are under heavy refactoring (github.com/pocketbase/poc…) and better/simpler APIs, including Go models generation, will be available in the next couple months (there are no ETAs yet)

@pocketbase is so cool, i thought it was just like supabase and didn't look into it all this time, i was wrong i can extend it with go and use it as a framework, that sold it to me 🙌

@CtrlAltIdeate It depends on how the browser was opened but if it doesn't have history, it will be auto-closed with JS on the redirect page. Alternatively if you use flutter_custom_tabs there is a closeCustomTabs method that you can invoke manually on OAuth2 completion (pub.dev/documentation/…)

@pocketbase Gotcha thank you! I don’t love the user being left hanging in the browser with the current flow but maybe I can figure something out.

@pocketbase are there any plans to support a native iOS / android oauth flow? Or has anyone out there hacked one together?

v0.22.14 Release - github.com/pocketbase/poc… This minor release allows retrieving the OAuth2 Apple account name and email and also address a security concern that was raised earlier today related to the OAuth2 autolinking with existing unverified email auth records.

@purbojatie There is no migrated tool as it will highly depend on the type and structure of your data. If you have an existing Supabase app then my recommendation is to stick with it because PocketBase is more limited and may not worth the required dev effort to perform the migration.

@pocketbase hello, can I migrate from supabase to pocketbase?

@luke_pighetti @digitalocean Then I'm probably not reading it correctly and thought it was related to github.com/pocketbase/poc….

@pocketbase @digitalocean The benchmarks exceeded my expectations. What makes you say something is wrong here?

basic load test @pocketbase on $5/mo @digitalocean VPC 150 concurrency (n=10k requests) select all from table (n=50 rows) 228 RPS @ 600ms 50%

@Mashwishi The JS SDK should work OK with React Native. For the realtime subscriptions you'll have to load an EventSource polyfill like react-native-sse or other (check the readme for more details). Also if you are testing on Android you may have to disable Flipper: #discussioncomment-6118523" target="_blank" rel="nofollow noopener">github.com/pocketbase/poc…

@pocketbase is pocket base friendly to react-native + expo?

v0.22.0 Release - github.com/pocketbase/poc… This release introduces back-relation filter/sort references, new Planning Center OAuth2 provider and some other minor improvements.

@doyouevenblog @HelloFresh That is most likely due to an old or buggy (ex. missing number glyphs) local installed Source Sans Pro font. The font-face declaration was updated to ignore the local version and it should be fixed now.

There are now 2 websites that show funky characters (another language?) instead of numbers/characters. First @HelloFresh , now @pocketbase. Anybody have any idea what's going on here? It's not every website.

@MadTJ84 The migrations (Go or JS) are usually the recommended approach for creating collections programmatically. Unapplied migrations are executed automatically on `serve`.

.@pocketbase - any recommendations for initializing a schema from code? I've read pocketbase.io/docs/go-collec…, I'm asking about practices for using that along with an init command or route to create and populate collections. Or should that be a migration action?