Comment on GitHub - voidauth/voidauth: An Easy to Use and Self-Host Single Sign-On Provider đââŹđ
lambalicious@lemmy.sdf.org â¨3⊠â¨weeks⊠agoIt does mean a form of provider lock-in, which is or can be its own issue. Also, while PostgreSQL is one of the best database engines out there among the FOSS stuff, it is verifiably and vastly overblown for stuff like âstore a name and a emailâ, and I at least am not aware of any sort of âPostgres Liteâ engines else Iâd be using them at work.
illusionist@lemmy.zip â¨3⊠â¨weeks⊠ago
How does it lock you in? You, the admin, has full control over postgres. Sqlite has no security features. Sqlite also locks the database which is usually OK if there are no concurrent jobs. But for such services it sounds like a bad idea to use sqlite. (I am no server/app dev)
lime_red@lemmy.world â¨3⊠â¨weeks⊠ago
Sqlite shouldnât lock for read, so unless you are writing something at each access, you can have thousands of concurrent reads. The Sqlite website spells this out, and lists its own self as the proof.
This would mean you could not write logs to the database, youâd have to do it the unixy way and put logs in a text file.
lambalicious@lemmy.sdf.org â¨2⊠â¨weeks⊠ago
It locks you to postgres. You donât necessarily have full control over postgres unless you are using your own instance / service, but oftentimes you might need to connect to an external one. SQLite gives you a local option.
Also what do you even mean with âdoes it store passwords?â A password is just a
TEXTor aBLOBif you are feeling charitable and SQLite does support those since forever. If you can store âhello worldâ you can store a password (just⌠donât do it in plaintext, but storage is different from encryption).