surtic86andClaude Opus 5
4530298398
- Config: auth, services, logging, queue and database only repeated the
framework's own files and are gone; the others keep only the keys that
differ (app version, cache serializable_classes, session cookie name,
Markdown mail theme, the shares disk, three Octane values, Livewire's
pagination theme and payload guards).
- Email verification is removed: User never implemented MustVerifyEmail,
so it was never enforced, and SealShare has a single admin and no
registration. CreateNewUser goes with it.
- FileEncryptionService::encryptFile() and generateSalt() were only used
by tests; tests build files with encryptTestFile() in tests/Pest.php.
- The expiration options are defined once, as Share::EXPIRATIONS. "30 Days"
now lasts 30 days instead of a calendar month, and Admin settings only
save a default expiration that is one of the options.
- One-caller helpers are inlined, the uploader reads chunk responses with
XHR's responseType, and starter-kit leftovers are removed.
- Docker: PHP reads the PHP_* limits from the environment itself
(${VAR:-default} in uploads.ini); both entrypoints stop writing the ini.
docker-compose.yml shares the app and scheduler variables through one
anchor. The dev image installs gd for the screenshot publisher and fake
test images.
- Development runs in Docker only: the composer dev script, concurrently,
laravel/pail, laravel/sail, autoprefixer and the shell-quote override
are gone.
- phpunit.xml forces the test environment with <server> entries, so tests
run in the dev container no longer use its real database.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
48 lines
1.5 KiB
PHP
48 lines
1.5 KiB
PHP
<?php
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Livewire
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Only what differs from Livewire's own config; every other key comes from
|
|
| its defaults. Livewire merges top-level keys only, so a nested key such
|
|
| as "payload" is given whole.
|
|
|
|
|
*/
|
|
|
|
return [
|
|
|
|
/*
|
|
|---------------------------------------------------------------------------
|
|
| Pagination Theme
|
|
|---------------------------------------------------------------------------
|
|
|
|
|
| livewire-material takes this over itself while it still reads as
|
|
| Livewire's own default ("tailwind", or the key missing), so this stays
|
|
| explicit: SealShare states the choice itself rather than relying on
|
|
| the package to silently switch it.
|
|
|
|
|
*/
|
|
|
|
'pagination_theme' => 'material',
|
|
|
|
/*
|
|
|---------------------------------------------------------------------------
|
|
| Payload Guards
|
|
|---------------------------------------------------------------------------
|
|
|
|
|
| Livewire's defaults, with at most 20 components per batch request
|
|
| instead of 200.
|
|
|
|
|
*/
|
|
|
|
'payload' => [
|
|
'max_size' => 1024 * 1024, // 1MB - maximum request payload size in bytes
|
|
'max_nesting_depth' => 10, // Maximum depth of dot-notation property paths
|
|
'max_calls' => 50, // Maximum method calls per request
|
|
'max_components' => 20, // Maximum components per batch request
|
|
],
|
|
|
|
];
|