mirror of
https://github.com/coollabsio/coolify.git
synced 2026-03-11 08:55:47 +00:00
chore(config): update inertia config to v3
This commit is contained in:
peaklabs-dev
parent
c5a061182d
commit
9415fe5bdb
1 changed files with 85 additions and 28 deletions
|
|
@ -3,6 +3,49 @@
|
|||
declare(strict_types=1);
|
||||
|
||||
return [
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Server Side Rendering
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| These options configures if and how Inertia uses Server Side Rendering
|
||||
| to pre-render the initial visits made to your application's pages.
|
||||
|
|
||||
| You can specify a custom SSR bundle path, or omit it to let Inertia
|
||||
| try and automatically detect it for you.
|
||||
|
|
||||
| Do note that enabling these options will NOT automatically make SSR work,
|
||||
| as a separate rendering service needs to be available. To learn more,
|
||||
| please visit https://inertiajs.com/server-side-rendering
|
||||
|
|
||||
*/
|
||||
|
||||
'ssr' => [
|
||||
'enabled' => (bool) env('INERTIA_SSR_ENABLED', true),
|
||||
|
||||
'url' => env('INERTIA_SSR_URL', 'http://127.0.0.1:13714'),
|
||||
|
||||
'ensure_bundle_exists' => (bool) env('INERTIA_SSR_ENSURE_BUNDLE_EXISTS', true),
|
||||
|
||||
// 'bundle' => base_path('bootstrap/ssr/ssr.mjs'),
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| SSR Error Handling
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| When SSR rendering fails, Inertia gracefully falls back to client-side
|
||||
| rendering. Set throw_on_error to true to throw an exception instead.
|
||||
| This is useful for E2E testing where you want SSR errors to fail loudly.
|
||||
|
|
||||
| You can also listen for the Inertia\Ssr\SsrRenderFailed event to handle
|
||||
| failures in your own way (e.g., logging, error tracking service).
|
||||
|
|
||||
*/
|
||||
|
||||
'throw_on_error' => (bool) env('INERTIA_SSR_THROW_ON_ERROR', false),
|
||||
],
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Pages
|
||||
|
|
@ -12,53 +55,67 @@ return [
|
|||
| components exist on disk when rendering a page. This is useful for
|
||||
| catching missing or misnamed components.
|
||||
|
|
||||
| The `page_paths` and `page_extensions` options define where to look
|
||||
| for page components and which file extensions to consider.
|
||||
| The `paths` and `extensions` options define where to look for page
|
||||
| components and which file extensions to consider.
|
||||
|
|
||||
*/
|
||||
|
||||
'ensure_pages_exist' => true,
|
||||
'pages' => [
|
||||
'ensure_pages_exist' => true,
|
||||
|
||||
'page_paths' => [
|
||||
resource_path('js/pages'),
|
||||
'paths' => [
|
||||
resource_path('js/pages'),
|
||||
],
|
||||
|
||||
'extensions' => [
|
||||
'svelte',
|
||||
'ts',
|
||||
],
|
||||
],
|
||||
|
||||
'page_extensions' => [
|
||||
'svelte',
|
||||
'ts',
|
||||
],
|
||||
|
||||
'use_script_element_for_initial_page' => (bool) env('INERTIA_USE_SCRIPT_ELEMENT_FOR_INITIAL_PAGE', true),
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Testing
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| The values described here are used to locate Inertia components on the
|
||||
| filesystem. For instance, when using `assertInertia`, the assertion
|
||||
| attempts to locate the component as a file relative to any of the
|
||||
| paths AND with any of the extensions specified here.
|
||||
| When using `assertInertia`, the assertion attempts to locate the
|
||||
| component as a file relative to the `pages.paths` AND with any of
|
||||
| the `pages.extensions` specified above.
|
||||
|
|
||||
| Note: In a future release, the `page_paths` and `page_extensions`
|
||||
| options below will be removed. The root-level options above
|
||||
| will be used for both application and testing purposes.
|
||||
| You can disable this behavior by setting `ensure_pages_exist`
|
||||
| to false.
|
||||
|
|
||||
*/
|
||||
|
||||
'testing' => [
|
||||
'ensure_pages_exist' => true,
|
||||
|
||||
'page_paths' => [
|
||||
resource_path('js/pages'),
|
||||
],
|
||||
|
||||
'page_extensions' => [
|
||||
'svelte',
|
||||
'ts',
|
||||
],
|
||||
],
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Expose Shared Prop Keys
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| When enabled, each page response includes a `sharedProps` metadata key
|
||||
| listing the top-level prop keys that were registered via `Inertia::share`.
|
||||
| The frontend can use this to carry shared props over during instant visits.
|
||||
|
|
||||
*/
|
||||
|
||||
'expose_shared_prop_keys' => true,
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| History
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Enable `encrypt` to encrypt page data before it is stored in the
|
||||
| browser's history state, preventing sensitive information from
|
||||
| being accessible after logout. Can also be enabled per-request
|
||||
| or via the `inertia.encrypt` middleware.
|
||||
|
|
||||
*/
|
||||
|
||||
'history' => [
|
||||
'encrypt' => (bool) env('INERTIA_ENCRYPT_HISTORY', true),
|
||||
],
|
||||
|
|
|
|||
Loading…
Reference in a new issue