29-08-2025 • 02:00 PM
Should I really use the multiple databases?
Today, I wasn't able to work a lot on the project design but I kept thinking about it. WICKET by design is supposed to use a separate postgres database then the main site of developer, that will be used only for storing authentication and profile related details, but this creates unnecessary overhead for small developers, maintaining, backup other stuff for multiple databases when your site is not scaled yet will be a pain in the ....
But I've decided to still go with it, to ensure the plug-n-play kind of system, and to be honest no line of code that I'm writing is permanent, this is my first big OSS project and I beleive everything will be changed in future depending upon the needs of WICKET's users, I can only future proof it till a certain time.
29-08-2025 • 12:56 AM
while designing the frontend, randomly a thought corssed my mind about developer experience when using wicket, providers like clerk have a lot of things already built for next js, where dev just have to copy paste just a few codes and they are good to go, but replicating that would be a big overhead for indie oss for me, I have finalized that I will go with providing only JWT tokens to the main site (wicket will be hosted on subdomain like accounts.example.com) and the main site can verify the authenticity easily using the secret string without even reaching wicket.
So, the only necessary reason to call wicket's API would to be generate new access tokens using refresh tokens and that's it, even though APIs for other things will be avaialbe.
28-08-2025 • 09:27 AM
I was able to design a lot of stuff today, but faced another big challenge, I'm still confused about how much customization should developer be allowed to make, like should it just be adding roles, or what if dev needs to add their custom groups and sets of permissions? like how will the developer using wicket be able to add coloumns in profile table? if I go full on customsable, would it still meet the main goal of plug and play?
For now I have decided to not go with any sorts of customization at all and tackle this problem in the phase 2 of development...
27-08-2025 • 12:09 PM
Today, I faced a challenge while designing a solution for logout from all devics,
my plan was to store refresh tokens in database and mark them expired when logged out from a device, but access tokens will still have some time till expiry in other devices, how will I make sure that access will be revoked instantly, I will have to find a solution
26-08-2025 • 01:05 AM
Everything planned, starting project design and development now