Poor Man's Back End-as-a-Service (BaaS), Similar to Firebase/Supabase/Pocketbase

Post by TekMol » Thu, Jul 03, 2025, 7:34 PM UTC

gausswho wrote: post #41

TekMol wrote: post #4

Do we still need a back-end, now that Chrome supports the File System Access API on both desktop and mobile? I have started writing web apps that simply store the user data as a file, and I am very pleased with this approach. It works perfectly for Desktop and Android. iOS does not allow for real Chrome everywhere (only in Europe, I think), so I also offer to store the data in the "Origin private file system" which a…

At least on the Android front, I'd prefer the app allow me to write to my own storage target. The reason is because I already use Syncthing-Fork to monitor a parent Sync directory of stuff (Obsidian, OpenTracks, etc.) and send to my backup system. In effect it allows apps to be local first and potentially even without network access, but allow me to have automatic backups. If there were something that formalized this…

Post by eatonphil » Thu, Jul 03, 2025, 7:59 PM UTC

riigess wrote: post #68

Calling this a Poor Man’s backend isn’t even the wrong name for it. Admittedly, this is what I’d expect from a Sophomore in University. To the others arguing you should’ve stored the data as a binary, might as well have created an API wrapper around SQLite at that rate and called it “JASW - Just Another Sqlite Wrapper”. @ OP - what was the inspiration for the project? Were you learning DBs or intending to use this in…

Post by [deleted] » Thu, Jul 03, 2025, 8:15 PM UTC

pavlov wrote: post #18

Why CSV instead of newline-separated JSON arrays? Ambiguity in your storage format isn’t good in the long run… JSON lines can be trivially parsed anywhere without a second thought.

Post by ehutch79 » Thu, Jul 03, 2025, 8:58 PM UTC

bob1029 wrote: post #52

fkyoureadthedoc wrote: post #5

> Another important file is _users.csv which contains user credentials and roles. It has the same format as other resources, but with a special _users collection name. There is no way to add new users via API, they must be created manually by editing this file: admin,1,salt,5V5R4SO4ZIFMXRZUL2EQMT2CJSREI7EMTK7AH2ND3T7BXIDLMNVQ====,"admin" alice,1,salt,PXHQWNPTZCBORTO5ASIJYVVAINQLQKJSOAQ4UXIAKTR55BU4HGRQ====, > Here we…

> isn't fast hashing like SHA-256 bad for it Fast hashing is only a concern if your database becomes compromised and your users are incapable of using unique passwords on different sites. The hashing taking forever is entirely about protecting users from themselves in the case of an offline attack scenario. You are burning your own CPU time on their behalf. In an online attack context, it is trivial to prevent an att…

Post by [deleted] » Thu, Jul 03, 2025, 9:05 PM UTC

pavlov wrote: post #18

Why CSV instead of newline-separated JSON arrays? Ambiguity in your storage format isn’t good in the long run… JSON lines can be trivially parsed anywhere without a second thought.