Server-Side Rendering
If you're concerned about diving into Inertia because your application requires server-side rendering, don't worry. Inertia offers server-side rendering support. And, when deploying your application via Laravel Forge, it's a breeze to ensure that Inertia's server-side rendering process is always running.
I am concerned with the following "when deploying your application via Laravel Forge, it's a breeze to ensure that Inertia's server-side rendering process is always running" does it mean would still have to run two servers in parallel similar to as if I would build a SPA?
@Sinnbeck, I thought for some reason that Inertia would take care of it. But looks like Inertia is just the glue between Front and Back you don't have to build APIs.
@tudosm Exactly yes. Thats the point of it. It makes it very very easy to integrate laravel as you use regular laravel routing. But you need the node server to run the javascript on the server :)
@Sinnbeck, may I ask why when I run Breeze & Blade starter kits and the last command is npm run dev I get prompted into a Vite development server http://localhost:5173/?
@tudosm That is something different (everything requires a server these days :)). Its a hot reload server. It allows you to edit your js and css without running npm run build every time. Instead it updates the code and automatically reloads the web page