Back to articles
I got tired of re-wiring the same boilerplate on every project so I built ForgeKit

I got tired of re-wiring the same boilerplate on every project so I built ForgeKit

via Dev.to WebdevSubhanshu Mohan Gupta

New project. Blank repo and here I am again, writing the same Dockerfile I wrote last month. Same GitHub Actions. Same ESLint config. Same docker-compose. Same test setup. I've done this so many times I could do it in my sleep. Which is exactly why I stopped doing it. I built ForgeKit . Run one command and your project is production-ready before you've had your first coffee. npm install -g forgekit-cli forgekit new my-app --template web-app 13 files. TypeScript configured. ESLint ready. Dockerfile written. docker-compose working. GitHub Actions running on your first push. Vitest set up. Nothing left to wire. You write code. Not config. What's included ⚡ CI/CD from commit one GitHub Actions wired and passing before you even open a PR. 📦 Docker, done Dockerfile and docker-compose ready to run locally and in prod. ✅ Tests configured Vitest is set up. You just write the tests. 📋 6 battle-tested templates Next.js, FastAPI, Go, ML pipeline, Serverless, and more. Pick your stack web-app : Nod

Continue reading on Dev.to Webdev

Opens in a new tab

Read Full Article
2 views

Related Articles