I love it when new tools challenge the giants. Sometimes, those repos with fewer stars and less popularity achieve more than the bigger ones.
Let's have it...
TanStack Start vs. Next
For context: I built Stunk–a state management library that is efficient!
a lot of people underestimate how strong arsenal is, tonight they will shock the world.... here is my prediction for the game.
.
.
#arsenal#ucl#psg#championsleague#uclfinal
I FIND A BETTER WAY DEPLOYING NEXTJS APP ON MY VPS.
We were burning CPU, RAM, and ~10GB of disk on our VPS every deploy building a large Next.js app directly on the server.
So we changed the model:
Build on GitHub Actions → push to GHCR → Dokploy pulls and runs.
No more yarn build on production. Deploys went from 15–20 minutes (when they didn’t fail) to seconds.
What changed: → Server = run containers, not compile code
→ Same image from staging (:release) to prod (:production)
→ Rollbacks = pull a previous tag
→ Freed ~10GB from old BuildKit cache alone
Same app. Cleaner ops.
If your VPS is still building Docker images on every push, you might not need a bigger server — you might need a different pipeline.