Hey guys, I will be launching a Next.js project with a friend of mine in a few days - a Dribbble-like website for 3D websites. We would like to start promoting it next week, my friend has a substantial following in the designers community (LinkedIn/Dribbble, etc.), so we're expecting a couple of hundred/thousand visits on the launch week.
I tried to fix as much stuff as possible function-wise (there are still some small UI fixes/inconsistencies needed to be addressed) and made sure not to burn myself with unexpected costs. The project is self-hosted on Hetzner VPS with Coolify and uses Supabase for auth/db (the paid plan, so we have backups, etc.).
It's the first Next.js project I have ever worked on (but I did some SvelteKit projects before), so I don't doubt at all that there might be some issues I missed. What would you recommend checking before going public? Do you follow any specific checklist? Do you use any AI tools to do such an audit? Thanks!
MetalGuru94 is preparing to launch a Next.js project and seeks advice on pre-release checks. The project is self-hosted on Hetzner VPS with Coolify and uses Supabase for authentication and database. The user is looking for recommendations on checklists or AI tools to ensure a smooth launch, anticipating significant traffic due to a partner's following.
Waf, cdn, authenticating in prod
Run lighthouse for perf stuff, check your headers with securityheaders.com, and make sure you're not exposing any server-side env vars to the client. If you used AI for any of the code try npx prodlint, it catches a lot of the stuff AI tends to get wrong like missing rate limiting and exposed error details.
this is unreasonably cool actually