> ## Documentation Index > Fetch the complete documentation index at: https://inertiajs.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Server-Side Setup The first step when installing Inertia is to configure your server-side framework. Inertia maintains an official server-side adapter for [Laravel](https://laravel.com/). For other frameworks, please see the [community adapters](/v3/installation/community-adapters). Inertia is fine-tuned for Laravel, so the documentation examples on this website utilize Laravel. For examples of using Inertia with other server-side frameworks, please refer to the framework specific documentation maintained by that adapter. Laravel's starter kits provide out-of-the-box scaffolding for new Inertia applications. These starter kits are the absolute fastest way to start building a new Inertia project using Laravel and Vue or React. However, if you would like to manually install Inertia into your application, please consult the documentation below. ## Installation First, install the Inertia server-side adapter using the Composer package manager. ```bash theme={null} composer require inertiajs/inertia-laravel ``` Next, create a `resources/views/app.blade.php` file. This root template will be loaded on the first page visit to your application. Inertia provides Blade components for rendering the head and body content. ```blade resources/views/app.blade.php theme={null} @vite('resources/js/app.js') ``` For React applications, it's recommended to include the `@viteReactRefresh` directive before the `@vite` directive to enable Fast Refresh in development. The `` component renders a `
` element with an `id` of `app`. This element serves as the mounting point for your JavaScript application. You may customize the `id` by passing a different value to the component. ```blade theme={null} ``` If you change the `id` of the root element, be sure to update it [client-side](/v3/installation/client-side-setup#defining-a-root-element) as well. The `` component also accepts [fallback content](/v3/the-basics/title-and-meta#ssr-fallback) via its slot for managing head elements when [SSR](/v3/advanced/server-side-rendering) is not active. By default, Inertia's Laravel adapter will assume your root template is named `app.blade.php`. You may change this using the `Inertia::setRootView()` method. Next we need to setup the Inertia middleware. You can accomplish this by publishing the `HandleInertiaRequests` middleware to your application, which can be done using the following Artisan command. ```sh theme={null} php artisan inertia:middleware ``` Once the middleware has been published, append the `HandleInertiaRequests` middleware to the `web` middleware group in your application's `bootstrap/app.php` file. ```php theme={null} use App\Http\Middleware\HandleInertiaRequests; ->withMiddleware(function (Middleware $middleware) { $middleware->web(append: [ HandleInertiaRequests::class, ]); }) ``` This middleware provides a `version()` method for setting your [asset version](/v3/advanced/asset-versioning), as well as a `share()` method for defining [shared data](/v3/data-props/shared-data). That's it, you're all ready to go server-side! Now you're ready to start creating Inertia [pages](/v3/the-basics/pages) and rendering them via [responses](/v3/the-basics/responses). ```php theme={null} use Inertia\Inertia; class EventsController extends Controller { public function show(Event $event) { return Inertia::render('Event/Show', [ 'event' => $event->only( 'id', 'title', 'start_date', 'description', ), ]); } } ``` ## Blade Directives Prior to v3, Inertia used `@inertiaHead` and `@inertia` Blade directives to render head and body content. These directives are still supported but do not offer SSR head [fallback content](/v3/the-basics/title-and-meta#ssr-fallback). The Blade components above are recommended for new applications. ```blade resources/views/app.blade.php theme={null} @vite('resources/js/app.js') @inertiaHead @inertia ``` You may customize the root element `id` by passing a value to the directive: `@inertia('custom-app-id')`.