PocketBase Profile Banner
PocketBase Profile
PocketBase

@pocketbase

4,176
Followers
0
Following
25
Media
94
Statuses

PocketBase - Open Source backend in 1 file

Joined July 2022
Don't wanna be here? Send us removal request.
@pocketbase
PocketBase
10 months
v0.20.0 Release - The most notable changes in this release are the filter, expand, custom query and header parameters support for the realtime subscriptions, new generalized logger, onlyVerified auth option and several other minor improvements and fixes.
Tweet media one
2
13
123
@pocketbase
PocketBase
2 years
Another great video by @fireship_dev : ps. Please note that it is using PocketBase v0.8. You should experience better performance and lower memory consumption with the the latest v0.10+ release.
3
11
110
@pocketbase
PocketBase
1 year
v0.17.0 Release - The biggest change in this release is the support of JavaScript app hooks and the new "Use as framework" guides. Make sure to check the release notes for more details.
Tweet media one
3
13
107
@pocketbase
PocketBase
1 year
v0.19.0 Release - This is a small release that brings Patreon and mailcow OAuth2 clients and several Admin UI improvements - optimized records listing for larger datasets (1M+), editor "Media library", option to open the record form via direct url, etc.
Tweet media one
1
15
107
@pocketbase
PocketBase
1 year
v0.16.0 Release - This release comes with built-in auto backups (+ cron rotation) APIS and UI, `?fields` query parameter support to return a subset of the json response fields, helper admins managing console command, and other minor improvements.
Tweet media one
5
19
98
@pocketbase
PocketBase
2 years
v0.13.0 Release - This release introduces a new "view" collection type, allowing you to create a read-only collections from any SQL SELECT statement (aggregations, subqueries, CTEs, etc.), while still maintaining the same List and View collection APIs.
Tweet media one
4
9
97
@pocketbase
PocketBase
1 year
v0.18.0 Release - This release comes with simplified serve command usage, backups zip generation speedup, option to upload backups from the Admin UI, wildcard (*) support for the fields parameter and several other internal improvements.
Tweet media one
4
8
91
@pocketbase
PocketBase
8 months
v0.22.0 Release - This release introduces back-relation filter/sort references, new Planning Center OAuth2 provider and some other minor improvements.
Tweet media one
4
7
92
@pocketbase
PocketBase
1 year
v0.15.0 Release - This release comes with support for token protected files, simplified OAuth2 integration (without the need of custom redirects, deeplinks or even page reload) and other minor UI improvements.
Tweet media one
2
14
85
@pocketbase
PocketBase
2 years
v0.12.0 Release - This release comes with refactored relation picker UI, option to customize the listing relation field(s), new rich text editor field (TinyMCE) and other various code improvements.
Tweet media one
5
6
83
@pocketbase
PocketBase
9 months
v0.21.0 Release - This is a small maintenance release introducing new Bitbucket OAuth2 provider, better json payload handling with multipart/form-data requests and other minor improvements.
Tweet media one
2
9
80
@pocketbase
PocketBase
2 years
v0.11.0 Release - This release comes with various API rules, filters and fields enhancements. Make sure to read the release notes before updating (there is small breaking change if you have multi-relation filters in your client-side code).
Tweet media one
0
9
63
@pocketbase
PocketBase
2 years
v0.14.0 Release - This release introduces unique constraints and indexes management (including multiple fields and expressions), relation normalizations and optimizations, experimental Apple OAuth2 integration, and other various improvements.
Tweet media one
4
5
60
@pocketbase
PocketBase
4 months
v0.22.14 Release - 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.
1
3
60
@pocketbase
PocketBase
2 years
v0.10.0 Release - This release comes with major performance improvements and reduced memory allocations (~20%). There are no breaking changes to the public web APIs. For more information, please refer to the release notes.
Tweet media one
2
5
51
@pocketbase
PocketBase
2 years
v0.9.0 Release - This release comes with several internal code improvements and the long-awaited automigrate feature. There are no breaking changes to the public apis. For more details please refer to the release notes in the link above.
Tweet media one
6
8
46
@pocketbase
PocketBase
2 years
v0.8.0 pre-release - This a dev preview for the upcoming v0.8.0 release. It comes with a lot of improvements (unfortunately some breaking), but the biggest one is the simplified users management apis and the support for different auth collections.
1
2
40
@pocketbase
PocketBase
2 years
v0.8.0 Release - There are no breaking changes if you've already migrated to v0.8.0-rc. If you are using PocketBase v0.7.x please follow the migration guide in the link above. btw. The site documentation was also updated -
Tweet media one
0
7
39
@pocketbase
PocketBase
2 years
First public release 🎉 PocketBase () is open source backend consisting of: - embedded database with realtime subscriptions - backed-in files and users management - convenient Admin dashboard UI - and simple REST-ish API All of this in 1 portable file!
Tweet media one
2
5
22
@pocketbase
PocketBase
2 years
v0.7.0 Release - This is mostly a maintenance release in preparations for v0.8.0, which will include some breaking changes to the users and records services in an attempt to simplify the existing workflow.
Tweet media one
0
4
20
@pocketbase
PocketBase
2 years
v0.6.0 Release - This release comes with: - improved mimetype sniffing support - Discord OAuth2 provider - Twitter OAuth2 provider - auto generated plaintext version of the emails HTML - and other minor improvements...
Tweet media one
0
0
13
@pocketbase
PocketBase
1 year
@iszuddin Just a side note to prevent eventual misunderstanding - PocketHost is a seperate project maintained by and it is not directly related to the PocketBase development (everyone is free to offer PocketBase as a service if they want to).
1
0
12
@pocketbase
PocketBase
2 years
v0.4.0 Release - The major new features in this release are related to the "Import/Export" of collections schema and allowing custom insertion ids for local/offline first data operations.
Tweet media one
0
0
13
@pocketbase
PocketBase
8 months
@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.
1
1
12
@pocketbase
PocketBase
2 years
Official Multi-platform Dart SDK for interacting with the PocketBase API is now publicly available -
Tweet media one
0
2
11
@pocketbase
PocketBase
2 years
v0.5.0 Release - This releases includes several improvements: - new thumb resizing options - support to customize the default user mail templates from the Admin UI - option to send test emails - new NOW datetime filter constant - ...
Tweet media one
0
2
10
@pocketbase
PocketBase
1 year
@athanazio The operator should be just single "=" and not "==". You could find a list with all supported operators in .
1
0
9
@pocketbase
PocketBase
2 years
v0.2.0 Release -
Tweet media one
1
2
9
@pocketbase
PocketBase
2 years
@JamesTurnerDev Yes, if you want to use a JS variable, aka. template literal/string interpolation, it is required to wrap it with backticks. The above expression is converted to the query parameter (url encoded): ?filter=name="vName value".
1
0
8
@pocketbase
PocketBase
2 years
v0.3.0 Release - The release includes non-nullable field values (minor breaking change!) and numerous Admin UI improvements.
Tweet media one
0
0
8
@pocketbase
PocketBase
8 months
@MadTJ84 The migrations (Go or JS) are usually the recommended approach for creating collections programmatically. Unapplied migrations are executed automatically on `serve`.
0
0
6
@pocketbase
PocketBase
2 years
@luke_pighetti PocketBase comes with auto Let's encrypt generation if you have a valid domain name and started with the --https flag: ./pocketbase --http="" --https="" More info could be found in
0
0
5
@pocketbase
PocketBase
2 years
@mlusetti Unfortunately, currently the JS migration API is not documented (it will be done in v0.13/v0.14 together with the planned JS hooks support ), but you can use the Go APIs as a reference. I've created a discussion with example in
1
0
5
@pocketbase
PocketBase
2 years
@Nanthony95 @kitsonk @deno_land @Nanthony95 @deno_land Hi, Just to let you know that the SDK core was rewritten in v0.2.0 and the axios dependency was replaced with `fetch()` so it should be a lot easier to load in Deno (as a bonus the bundle size was also reduced almost 4 times to ~5kb gzipped).
0
1
4
@pocketbase
PocketBase
9 months
@biki636 No sorry, there are no fixed ETAs or deadlines.
0
0
3
@pocketbase
PocketBase
2 years
@yourboykino @fireship_dev It depends on a lot of factors. In an optimized configuration (eg. listening on unix socket instead of proxying tcp), in general it could help providing better availability, but most of the time you'll get better performance by directly accessing the the Go server.
0
0
3
@pocketbase
PocketBase
2 years
@RichardMace While it is possible to connect to the pb_data/data.db file from other processes/applications, direct changes in the db file will not trigger the realtime events. Depending on your use case, it may be better to just "embed" PocketBase in your Go app - .
0
0
3
@pocketbase
PocketBase
1 year
@meltinbit The manual PKCE code exchange flow is still supported and there is nothing wrong with it (internally it is still used). The new version just makes the integration slightly less verbose and handles the cases where an app redirect/deeplink is not possible (eg. Figma plugins)
0
0
3
@pocketbase
PocketBase
2 years
@danieldogeanu It is a false positive and unfortunetely there is no reliable way to prevent this from happening. Go even has an official section for this in their FAQ -
1
0
3
@pocketbase
PocketBase
1 month
@brainage19 You can rule out PocketBase issue by testing with a different SMTP provider like or . For Gmail see also . In all cases, I don't recommend entering your SMTP credentials in random online forms.
1
0
3
@pocketbase
PocketBase
1 year
@danieldogeanu @karim_mev API keys were suggested in the past and it exists in my todo to consider but for now remains a low priority due to some security concerns related to their implementation. For a recommended "auth as admin" approach, you could check the example in .
1
0
2
@pocketbase
PocketBase
2 years
@JamesTurnerDev There are plans in the future to also add an optional builder that would help with programatically constructing the filter expression, eg. something like: pb.collection("example").getFirstListItem(pb.filter().eq("name", vName))
1
0
2
@pocketbase
PocketBase
2 years
@_mvalentinee There are no breaking changes to the public web apis. If you already are using v0.8, then you can just replace the binary with the new one. If you are embedding PocketBase in your Go app, please refer to the changelog for details on the changed exported internal apis.
0
0
2
@pocketbase
PocketBase
1 year
@stphnjet The Dart SDK also uses the web APIs under the hood so if you have a OnRecordBeforeCreateRequest hook it should get triggered on pb.collection("example").create(...) call.
1
0
2
@pocketbase
PocketBase
2 months
@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.
0
0
3
@pocketbase
PocketBase
1 year
@stphnjet We don't provide hosting and developers are free to manage their deployment environments however they want. If you need further help, feel free to post a Q&A discussion with more details in
1
0
2
@pocketbase
PocketBase
1 year
@stphnjet PocketBase comes with auto migrations out of the box. It is enough both projects to use the same `pb_migrations` dir to have the same db schema. If you want both env to share the same data then you can copy directly the `pb_data` dir. You can check
0
0
2
@pocketbase
PocketBase
2 years
@hypersonic90104 @fireship_dev Hi! You don't need external orm to work with PocketBase. We have advanced query support via a simple filter syntax, eg.: "status = 'pending' || status = 'active'". You can even query nested relation fields, eg. `someRel.totalComments > 100` (check )
1
0
2
@pocketbase
PocketBase
2 years
@zaki_chahboun 1. It depends on your requirements, but if I have to generalize - Yes, small and mid size app should be fine (PocketBase was created initially for Presentator - ) 2. Please check .
0
0
2
@pocketbase
PocketBase
7 months
@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:
0
0
2
@pocketbase
PocketBase
3 months
@ajmalmohad_ Side-note: Be aware that the current Go frameworks APIs are under heavy refactoring () and better/simpler APIs, including Go models generation, will be available in the next couple months (there are no ETAs yet)
1
0
2
@pocketbase
PocketBase
4 months
@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 ()
1
0
1
@pocketbase
PocketBase
5 months
@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.
0
0
0
@pocketbase
PocketBase
1 year
@stphnjet No, sorry there are no fixed ETAs at the moment.
2
0
1
@pocketbase
PocketBase
4 months
@CtrlAltIdeate If you mean native Google and Apple auth, then No (at least not out of the box) as it will differ too much from the current OAuth2 integration. The existing flow (practically a single authWithOAuth2 function call) should be already easy and sufficient enough for most of the cases
1
0
1
@pocketbase
PocketBase
2 years
@luke_pighetti Yes, you can expanded nested relation with a dot notation (eg. `?expand=relA.subRel1.subRel2`). Note that the relation records will be expanded only if "view" API rule is satisfied. Additionally, soon we will have support for indirect expands -
0
0
1
@pocketbase
PocketBase
2 years
@satanworker @fireship_dev Yes, you can find the API documentation under the "Web APIs" section in the sidebar in .
0
0
1
@pocketbase
PocketBase
2 years
@US_Khokhar Discontinued before even started :D Joking aside, you can find docs how to deploy your PocketBase app in
1
0
1
@pocketbase
PocketBase
2 years
@luke_pighetti Thanks, I wasn't aware of the iOS requirement. There is an open issue for adding Apple OAuth2 provider in . I'll consider it after the ongoing users management refactoring.
0
0
1
@pocketbase
PocketBase
2 years
@mlusetti Yes, but you'll have to register the js migrations loader in your Go app before the migratecmd command. For an example you can check the prebuilt executable go main file:
1
1
1
@pocketbase
PocketBase
2 years
@kyrill_bo If I'm understanding correctly your use case, you have 2 options: 1. Use the "?" ("at least one of") operators, eg.: ` ?= "${userId}"` 2. Use the "~" contain/like operator against the serialized value: `users ~ "${userId}"`
1
0
1
@pocketbase
PocketBase
2 years
@qiqete Hi! It's already in the roadmap and will be handled after the ongoing users management refactoring. You can subscribe to this issue -
0
0
1
@pocketbase
PocketBase
2 years
@adophilus I'm not familiar with your use case, but you don't have to use Go if you don't want to. You can use the Records API to filter/search your collection records with any language. You could check
1
0
1
@pocketbase
PocketBase
1 month
@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.
0
0
1
@pocketbase
PocketBase
2 years
@luke_pighetti You could create a new relation field to "profiles" and use that as a reference to the users, then you'll be able to expand them via `?expand=rel1,rel2` (if you have "view" access to the collection). User fields cannot be expanded. This will be fixed in
1
0
1
@pocketbase
PocketBase
2 years
@Infante_SD Technically it is in the roadmap after the discussion in , but for now it has the lowest priority and may or may not be implemented for v1.
0
0
1
@pocketbase
PocketBase
2 years
@US_Khokhar Render storage by default is ephemeral and for persistence you'll have to mount Disks -
0
0
1
@pocketbase
PocketBase
8 months
@0xCamo @what_the_func @ImSh4yy Note that the auth and user create requests will be "rate limited" by default as a side effect of the bcrypt hash generation and verification (on most servers this usually means ~2 req/sec). For more advanced network controls you can put PocketBase behind a reverse proxy.
1
0
1
@pocketbase
PocketBase
2 years
@HeyClos Thank you, I've pushed a fix.
1
0
1
@pocketbase
PocketBase
1 year
@blake_dzc @DmytroKrasun Litestream should work fine with PocketBase as long as you point it to the db file located in `pb_data/data.db`.
0
0
1