moh_quz

6 ms·

1.
Show HN: Agentic Ship – open-source Lovable alternative that runs on your agent(github.com)
2 points by moh_quz 1mo ago|0 comments
2.
by moh_quz 9mo ago
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 deployment, and then I wrote scripts auto
3.
by moh_quz 9mo ago
You are welcome hope it benefits you!
4.
by moh_quz 9mo ago
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, billing, database, everything. Next is
5.
by moh_quz 9mo ago
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 connect it to the same Go backend. Only thin
6.
by moh_quz 9mo ago
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 for any questions!
7.
by moh_quz 9mo ago
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
8.
by moh_quz 9mo ago
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 spot anything in the repo or have ideas,
9.
by moh_quz 9mo ago
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
10.
by moh_quz 9mo ago
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, including me. Win-win. Your IAM separation i
11.
by moh_quz 9mo ago
You are more than welcome! If you need anything don’t hesitate to reach out, you can find my info in the repo
12.
by moh_quz 9mo ago
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.
13.
by moh_quz 9mo ago
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 are guides for where to add your own co
14.
by moh_quz 9mo ago
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. Merchant of Record means I don't thi
15.
by moh_quz 9mo ago
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 adapter). If I swap Stytch for Ory or Auth0,
16.
by moh_quz 9mo ago
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 compute separately from frontend serving.
17.
Show HN: I open-sourced my Go and Next B2B SaaS Starter (deploy anywhere, MIT)(github.com)
83 points by moh_quz 9mo ago|35 comments
18.
Show HN: Open-Source B2B SaaS Starter Kit (Go, Next.js, RBAC, Polar)(github.com)
1 points by moh_quz 9mo ago|0 comments
19.
Show HN: Open Source B2B SaaS Starter Kit (Go, Next.js, RBAC, Polar)(github.com)
1 points by moh_quz 9mo ago|1 comments
20.
by moh_quz 9mo ago
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-source my internal kit (MIT Licensed) to
21.
by moh_quz 9mo ago
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. a boring docker compose setup usually so
22.
by moh_quz 9mo ago
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.
23.
by moh_quz 9mo ago
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 that machine (or proxying through it).
24.
by moh_quz 9mo ago
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 between steps? Does it persist to the DB afte
25.
by moh_quz 9mo ago
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 looking into stricter egress filtering