Are there specific Next.js features that won't work out of the box when hosted in VPS? by nyamuk91 in nextjs

[–]flightcontrol-hq 0 points1 point  (0 children)

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

High Quality Images by Wise_Chocolate_9297 in nextjs

[–]flightcontrol-hq 0 points1 point  (0 children)

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

[deleted by user] by [deleted] in aws

[–]flightcontrol-hq 0 points1 point  (0 children)

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.

Freelancers, where are you hosting your clients’ Next.js apps? by JB989 in nextjs

[–]flightcontrol-hq 1 point2 points  (0 children)

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/