So is this to nango what better-auth is to clerk? Like handshake.cool?
I suggest writing your documentation from the perspective of someone maintaining separation of concerns between their backend (e.g like hono) and the frontend (react).
How would I integrate this with my existing hono+drizzle api? The docs mention prisma but cannot find the implementation in the example web app repo.
Generally, the deeper the tool abstracts, the more idiot(me)-proof the documentation should be.
I wouldn’t quite make that analogy. Nango has a great open source culture and does what it does really well but self hosting their entire infrastructure would be hell. The difference with Databite is that I’m trying to make the idea of managing integrations with data syncs as easy as spinning up an Express server.
Appreciate you taking the time to read the docs. You’re right the example app’s implementation is currently incomplete and parts of the docs describe the intended dev experience rather than what’s currently implemented in the repo.
I’m pushing a major update to both the packages and docs in the next half day and would love your feedback once it’s live. I'll try my best to make the READMEs and docs as simple to follow as possible!!
Thank you for bringing Handshake to my attention, I'll try implement it when I get the time. From a quick readthrough of their readme, Handshake looks like such a great project and definitely solves one of the hardest parts of building integrations which is auth but I'd like to take Databite a step further and include scheduling of syncs, calling of actions and the handling of webhooks.
So is this to nango what better-auth is to clerk? Like handshake.cool?
I suggest writing your documentation from the perspective of someone maintaining separation of concerns between their backend (e.g like hono) and the frontend (react).
How would I integrate this with my existing hono+drizzle api? The docs mention prisma but cannot find the implementation in the example web app repo.
Generally, the deeper the tool abstracts, the more idiot(me)-proof the documentation should be.
I wouldn’t quite make that analogy. Nango has a great open source culture and does what it does really well but self hosting their entire infrastructure would be hell. The difference with Databite is that I’m trying to make the idea of managing integrations with data syncs as easy as spinning up an Express server.
Appreciate you taking the time to read the docs. You’re right the example app’s implementation is currently incomplete and parts of the docs describe the intended dev experience rather than what’s currently implemented in the repo.
I’m pushing a major update to both the packages and docs in the next half day and would love your feedback once it’s live. I'll try my best to make the READMEs and docs as simple to follow as possible!!
Thank you for bringing Handshake to my attention, I'll try implement it when I get the time. From a quick readthrough of their readme, Handshake looks like such a great project and definitely solves one of the hardest parts of building integrations which is auth but I'd like to take Databite a step further and include scheduling of syncs, calling of actions and the handling of webhooks.