Here's the stack:
Backend: Go, Gin, JWT auth, PostgreSQL (hosted on Neon.tech), Cloudinary for image uploads
Frontend: React + Tailwind CSS
I haven't actually clicked deploy yet. This post is me writing it down before I do it, partly to hold myself accountable and partly because I have a feeling something's going to break — probably CORS, probably env variables, probably something dumb I'll laugh at in a week.
Question for you all
If you've deployed a Go API + React frontend combo before — did you go with Railway + Vercel, or something else entirely ?
And if you've done something different from the ones i want to work with, I would genuinely love to hear about it before I find out the hard way.
Top comments (1)
"This post is me writing it down before I do it, partly to hold myself accountable" — I love this move. Writing it down BEFORE the scary button is a real technique, not just a bit.
I still remember my first move to a real server. I'm not even a developer (physical therapist who builds internal tools with AI), and I spent a whole week with my shoulders up around my ears, triple-checking I'd logged out of the admin account every evening. And you're right about the prediction: something did break, it was config, and I did laugh about it later.
Two things that helped me since: (1) deploy the smallest possible slice first — one endpoint, one page — so when it breaks you know roughly where to look, and (2) keep a dumb little log of every fix, because deploy #2 goes twice as fast when deploy #1 is written down. Good luck — come back and tell us what actually broke. That's the post I want to read.