Some checks failed
CI / PHP 8.3 / mariadb:10.6 (pull_request) Successful in 1m14s
CI / PHP 8.4 / mariadb:10.6 (pull_request) Successful in 1m12s
CI / PHP 8.4 / mariadb:11.4 (pull_request) Successful in 1m7s
CI / PHP 8.3 / mariadb:11.4 (pull_request) Successful in 1m19s
CI / PHP 8.3 / mysql:8.0 (pull_request) Successful in 1m32s
CI / PHP 8.4 / mysql:8.0 (pull_request) Successful in 1m22s
CI / PHP 8.4 / mysql:8.4 (pull_request) Successful in 1m32s
CI / PHP 8.3 / mysql:8.4 (pull_request) Successful in 1m35s
CI / Build-Artefakte aktuell (pull_request) Failing after 1m7s
- Laravel 13 mit Filament 5 (Admin), Inertia 3 + Vue 3 + Vuetify 4 (Material 3) - Anmeldung über Fortify (Login, Passwort vergessen/ändern), keine Selbstregistrierung - Profil mit Profilbild (WebP in festen Größen), Personenseiten, Header mit Avatar-Menü - Material-3-Farbschema aus der Primärfarbe, hell/dunkel/System pro Person - Basis-Branding (Portalname, Logo, Primärfarbe) im Admin unter „Erscheinungsbild“ - Benutzerverwaltung im Admin, Zugang vorläufig über is_admin - vendor/ (ohne Dev-Pakete) und Frontend-Build mitversioniert, Dev-Pakete in vendor-dev/ - PHPUnit-Tests gegen MySQL/MariaDB, Forgejo-CI-Matrix, Docker-Entwicklungsumgebung - VERSION, CHANGELOG.md und CONTRIBUTING.md mit Release-Ablauf Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
137 lines
4.6 KiB
PHP
137 lines
4.6 KiB
PHP
<?php
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Broadcasting
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| By uncommenting the Laravel Echo configuration, you may connect Filament
|
|
| to any Pusher-compatible websockets server.
|
|
|
|
|
| This will allow your users to receive real-time notifications.
|
|
|
|
|
*/
|
|
|
|
'broadcasting' => [
|
|
|
|
// 'echo' => [
|
|
// 'broadcaster' => 'pusher',
|
|
// 'key' => env('VITE_PUSHER_APP_KEY'),
|
|
// 'cluster' => env('VITE_PUSHER_APP_CLUSTER'),
|
|
// 'wsHost' => env('VITE_PUSHER_HOST'),
|
|
// 'wsPort' => env('VITE_PUSHER_PORT'),
|
|
// 'wssPort' => env('VITE_PUSHER_PORT'),
|
|
// 'authEndpoint' => '/broadcasting/auth',
|
|
// 'disableStats' => true,
|
|
// 'encrypted' => true,
|
|
// 'forceTLS' => env('VITE_PUSHER_SCHEME', 'https') === 'https',
|
|
// ],
|
|
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Default Filesystem Disk
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This is the storage disk Filament will use to store files. You may use
|
|
| any of the disks defined in the `config/filesystems.php`.
|
|
|
|
|
*/
|
|
|
|
'default_filesystem_disk' => env('FILESYSTEM_DISK', 'local'),
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Temporary File URL Expiry
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| When Filament generates temporary URLs for previewing private files
|
|
| (file uploads, image columns, image entries, rich editor attachments,
|
|
| etc.), this value controls how many minutes those URLs remain valid.
|
|
|
|
|
| The generated URL's expiry is rounded up to the end of the hour it
|
|
| falls in, so the effective lifetime will be between this value and
|
|
| this value plus up to 60 minutes.
|
|
|
|
|
*/
|
|
|
|
'temporary_file_url_expiry_minutes' => 30,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Assets Path
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This is the directory where Filament's assets will be published to. It
|
|
| is relative to the `public` directory of your Laravel application.
|
|
|
|
|
| After changing the path, you should run `php artisan filament:assets`.
|
|
|
|
|
*/
|
|
|
|
'assets_path' => null,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Cache Path
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This is the directory that Filament will use to store cache files that
|
|
| are used to optimize the registration of components.
|
|
|
|
|
| After changing the path, you should run `php artisan filament:cache-components`.
|
|
|
|
|
*/
|
|
|
|
'cache_path' => base_path('bootstrap/cache/filament'),
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Livewire Loading Delay
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This sets the delay before loading indicators appear.
|
|
|
|
|
| Setting this to 'none' makes indicators appear immediately, which can be
|
|
| desirable for high-latency connections. Setting it to 'default' applies
|
|
| Livewire's standard 200ms delay.
|
|
|
|
|
*/
|
|
|
|
'livewire_loading_delay' => 'default',
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| File Generation
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Artisan commands that generate files can be configured here by setting
|
|
| configuration flags that will impact their location or content.
|
|
|
|
|
| Often, this is useful to preserve file generation behavior from a
|
|
| previous version of Filament, to ensure consistency between older and
|
|
| newer generated files. These flags are often documented in the upgrade
|
|
| guide for the version of Filament you are upgrading to.
|
|
|
|
|
*/
|
|
|
|
'file_generation' => [
|
|
'flags' => [],
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| System Route Prefix
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This is the prefix used for the system routes that Filament registers,
|
|
| such as the routes for downloading exports and failed import rows.
|
|
|
|
|
*/
|
|
|
|
'system_route_prefix' => 'filament',
|
|
|
|
];
|