Three days ago, GolangForAll didn’t exist. Neither did GoLab.
On September 17, I started the WeMakeDevs Bharat Builds Tour hackathon completely solo — just a laptop, an idea, and a deadline.
I didn’t want to build another hackathon demo that works only for judging.
I wanted to build something people could actually use.
So I started with GolangForAll — a Go community, along with a custom blog, admin panel, and documentation platform.
Then came GoLab.
A browser-based Go playground where you can write code, provide input, and run it instantly — with actual Go compilation and execution happening inside an isolated Docker sandbox.
The interesting part wasn’t just getting it to work.
It was getting it to production.
I deployed the backend on AWS EC2, configured the domain and routing, added a reverse proxy, and built the entire execution pipeline around isolated containers with restricted capabilities, non-root execution, read-only filesystems, resource limits, and timeouts.
And yes, things broke.
At one point, stdin simply wasn’t reaching the program.
Hours of debugging eventually came down to one missing Docker flag.
Fixed it. Shipped it.
By September 19, the community, blog, docs, playground, backend, hosting, and infrastructure were all live.
Built solo. Shipped in 3 days.
The biggest thing I learned wasn’t about AWS, Docker, Go, or deployment.
It was that you can start with very little and still build something real — one problem at a time.
Loading article