Nextjs tips
Unanswered
French Lop posted this in #help-forum
French LopOP
Does anyone have some good insights on their nextjs setup. Im reading online that some people run Hono for their API routes but most of thosr articles are 8 months old so pre nextjs 16. Is this still something I should consider? Im currently depliying everything via docker / docker compose sincr my server has Coolify on it. Are there limitations to the standalonr output and what are some good practices to keep in mind. Im using Drizzle ORM + Redis Cache (depends on the project) and BetterAuth on all my projects. Am I missing steps? Also any other thinga that yall use different providers for just like Hono for API or does everyone keep it nextjs native. Please tag me if anyone has some nice insights so I dont miss them 😄 Any and all info is greatly appreciated
4 Replies
@French Lop Does anyone have some good insights on their nextjs setup. Im reading online that some people run Hono for their API routes but most of thosr articles are 8 months old so pre nextjs 16. Is this still something I should consider? Im currently depliying everything via docker / docker compose sincr my server has Coolify on it. Are there limitations to the standalonr output and what are some good practices to keep in mind. Im using Drizzle ORM + Redis Cache (depends on the project) and BetterAuth on all my projects. Am I missing steps? Also any other thinga that yall use different providers for just like Hono for API or does everyone keep it nextjs native. Please tag me if anyone has some nice insights so I dont miss them 😄 Any and all info is greatly appreciated
Coolify handles nextjs projects very well. Use nixoacks even when you had issues in the past. Don’t try to handle anything with docker or similar while using coolify. If you really want to self host, but decided to NOT use coolify, then “le rob” has a great tutorial for it on YouTube. Enter the video, check the description, take a look at his readme and his configuration and do it the same.
In both scenarios there are no limitations. Your tech stack is independent of that, so no worries.
Having the backend separated from the frontend is a common strategy. Do whatever suites best for you
In both scenarios there are no limitations. Your tech stack is independent of that, so no worries.
Having the backend separated from the frontend is a common strategy. Do whatever suites best for you
@B33fb0n3 Coolify handles nextjs projects very well. Use nixoacks even when you had issues in the past. Don’t try to handle anything with docker or similar while using coolify. If you really want to self host, but decided to NOT use coolify, then “le rob” has a great tutorial for it on YouTube. Enter the video, check the description, take a look at his readme and his configuration and do it the same.
In both scenarios there are no limitations. Your tech stack is independent of that, so no worries.
Having the backend separated from the frontend is a common strategy. Do whatever suites best for you
French LopOP
Any reasons for splitting the api to a hono server? Even when NextJS is specifically designed for full stack?
I will try Nixpacks again when I get back from my holiday
@French Lop Any reasons for splitting the api to a hono server? Even when NextJS is specifically designed for full stack?
Yes, many people like to use it to keep single responsibility principle. IMO nextjs is great and works like that too when you set it up correctly. But many people also say that nextjs overpowered and they just need (for example) route handlers. And just for that others are way better