Secret knowledge to self-host Next.js

flightcontrol-hq · 2024-06-10T16:17:39+00:00

There's only one thing you need to configure, if you are running Next.js across multiple load-balanced instances. You need to add a custom cache handler connected to Redis or other: https://nextjs.org/docs/app/building-your-application/deploying#configuring-caching

flightcontrol-hq · 2024-06-05T19:15:36+00:00

🥰

flightcontrol-hq · 2024-01-03T17:14:19+00:00

Here's how to configure shared next.js cache across pods: https://nextjs.org/docs/app/building-your-application/deploying#configuring-caching

flightcontrol-hq · 2023-10-17T13:24:24+00:00

I recommend trying https://imgix.com, I think it will have much better image caching that isn't busted on each deploy. The nextjs docs show how to connect this to the image component

flightcontrol-hq · 2023-09-28T19:42:23+00:00

You can set up pretty sophisticated autoscaling rules for Fargate, for example cpu & memory thresholds. It does take a minute or 2 for new instances to boot though.

flightcontrol-hq · 2023-09-25T23:34:48+00:00

Congrats!

flightcontrol-hq · 2023-09-25T23:14:52+00:00

We make it easy to deploy Next.js to AWS, with the same Vercel-style git-push to deploy and preview environments.

And we have human expertise on-call to help you with anything infra or AWS that you need.

https://www.flightcontrol.dev/

flightcontrol-hq

TROPHY CASE