lalitgehani

4 ms·

1. 1.▲
   by lalitgehani 9mo ago

   Haha, good eye! That's actually just a standard component from Mintlify, which I'm using for the documentation. It’s a very popular framework for dev tools right now, so a lot of sites end up sharing the same standard icon set lik
2. 2.▲
   by lalitgehani 9mo ago

   I completely get the fatigue. We’re seeing a lot of "one-shot" projects right now that look great for a week and then die because there was no actual design behind the prompt. For SnackBase, I actually spent the majority of my tim
3. 3.▲
   by lalitgehani 9mo ago

   Thank you! That is exactly the "boilerplate tax" I’m trying to eliminate. I think every developer has a story about spending months on those exact features. Organizations, RBAC, Auth, etc. before they ever get to write a single li
4. 4.▲
   by lalitgehani 9mo ago

   Great question! Keybase's Merkle approach is elegant for their use case (efficient proofs without revealing the full chain), but I went simpler with a linear chain because: 1. Audit trails are inherently sequential - they're order
5. 5.▲
   by lalitgehani 9mo ago

   Fair point. Honestly, I picked AGPL mainly to prevent "cloud wrapping". I definitely don't intend for your business logic to get infected by it. In my view, the custom hooks and schemas are "content/configuration&qu
6. 6.▲
   by lalitgehani 9mo ago

   Thanks for the kind words and the bookmark! You're right. Since I use SQLAlchemy, the core is already database agnostic. Swapping the connection string to Postgres actually works for most features right now. I listed it as "Roadma
7. 7.▲
   Show HN: SnackBase – Open-source, GxP-compliant back end for Python teams(snackbase.dev)

   70 points by lalitgehani 9mo ago|14 comments