Menu

Running 48 Next.js sites from one laptop: what the tooling actually costs
πŸ“°

Running 48 Next.js sites from one laptop: what the tooling actually costs

DEV Community: nextjsΒ·zhaoqΒ·22 days ago
#s8UPabIW
#devtonextjs#devto#dev#sites#every
Reading 0:00
15s threshold

I did not set out to run 48 websites. It was supposed to be one.

A year ago I started a small wiki for an indie game β€” game guide pages, the kind of thing where "how do I beat this boss" gets 200 searches a month and nobody has written it down. That one site worked well enough that the obvious next move was a second, then a fifth, then a template and a script.

At 48 sites the problems stopped being about writing pages and started being about tooling. Here is what it actually costs, in case you are tempted to do the same thing.

The stack is boring, on purpose

Every site is the same Next.js app: static export, a content/guides/*.md folder, and three config files ( lib/seo-config.ts , lib/adsterra-zones.ts , lib/site.ts ). No database, no API routes, no server state.

That is the whole point. When 48 sites share one codebase shape, a fix is written once and applied 48 times. When they diverge, maintenance becomes a full-time job.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.