moh_quz

Thanks and appreciate your compliment! The deployment process for this repo has been really smooth for me. I use only docker compose, and traefik for web server. ngl I ran claude code to help me for d…

You are welcome hope it benefits you!

This is really helpful context, thanks for writing it out. You’re right that Next wants to be your backend and thats exactly why I kept the real backend separate in Go. The Go backend handles all auth…

Honestly just because its the most popular so more people can pick it up easily. But the frontend and backend arent tightly coupled at all. You can swap Next for Vite, Nuxt, whatever you want and conn…

Just checked yours, it is really helpful for those who want to start quickly, some people won't use mine because it is too much for their use case. Thanks for your feedback, and I am always open …

Tbh not yet, I heard that it’s more user friendly, but I go with gin because it has larger community and support! Would love to explore different libraries

Thanks man, really appreciate it! ConnectRPC looks interesting actually, proper API schema with generated TS client is nice. And that Nuxt dashboard template is clean, hadnt seen that before. If you s…

Fair point. For what its worth I did add a script that runs tests and checks coverage. But yeah the coverage itself could be better, working on it PRs welcome if anyone wants to help out

Thanks! That's exactly why I open-sourced it. Instead of this living in my private repo getting occasional updates, now the community can push it forward. Improvements flow back to everyone, incl…

You are more than welcome! If you need anything don’t hesitate to reach out, you can find my info in the repo

I really appreciate your comment, never hesitate to reach out to me if you have any concerns, you can find my info in the repo.

This was extracted from my production apps including (apflow.co). I stripped out the business logic and keys, then pushed it as a clean starting point. The "in production you would" comments…

Totally valid. The Go backend is just a REST API with no Next.js coupling. You could swap the frontend for Go templates + htmx without changing the backend at all. And yeah, Polar.sh has been great. M…

Fair question. The difference for me: Supabase lock-in is deep (their Postgres extensions, auth hooks, edge functions all intertwined). Stytch lock-in is shallow (just an API behind a ~200 line adapt…

You're not doing it wrong. For most CRUD apps, Next.js + tRPC is the right call. My tipping point was long-running tasks (OCR, AI processing that takes 30+ seconds) and wanting to scale backend c…

Hi HN, I realized I was spending the first 3 weeks of every new B2B project just wiring up "boring" infrastructure like Authentication, Team Invites, and Billing webhooks. I decided to open-…

the part about "shifting left" is spot on. feels like we just dumped all the ops complexity onto devs who just want to write code. honestly unless you're massive, k8s is just overhead. …

nice to see more go tooling. curious how you handled the lock-free part - was it mostly atomics or just clever channel usage? always found backpressure tricky to handle without locks.

That definitely helps, but I don't think it solves the compromised machine scenario. If the attacker has shell access to the dev's laptop, they are likely just running commands directly from…

This looks useful. I've been exploring similar durable execution patterns in Go recently to avoid the complexity of Temporal for smaller workflows. How does stepped_actions handle the state betwe…

Really appreciate the transparency here. Post-mortems like this are vital for the industry. I'm curious was the exfiltration traffic distinguishable from normal developer traffic? We've been…