Majority of the messages are in the format ":attribute must
{conditions_to_be_met}", however a few inconsistently use "may" instead
of "must".
This PR fixes that and has them all use "must" instead.
To highlight the inconsistency:
```php
// "may"
'max' => [
'numeric' => 'The :attribute may not be greater than :max.',
'file' => 'The :attribute may not be greater than :max kilobytes.',
'string' => 'The :attribute may not be greater than :max characters.',
'array' => 'The :attribute may not have more than :max items.',
],
// "must"
'min' => [
'numeric' => 'The :attribute must be at least :min.',
'file' => 'The :attribute must be at least :min kilobytes.',
'string' => 'The :attribute must be at least :min characters.',
'array' => 'The :attribute must have at least :min items.',
],
```
Inspired by https://github.com/laravel/framework/pull/36415
As JetStream/Fortify uses a `current_password` field when allowing a user to change their password, and as JetStream is one of the starter kits listed on the docs, this PR adds `current_password` in the `$except` option of the `TrimStrings` middleware.
* Added sans-serif as Fallback Font
Added sans-serif as Fallback Font to the Welcome Page
* Update welcome.blade.php
Co-authored-by: Taylor Otwell <taylor@laravel.com>
* Don't flash `current_password` input
With starter packs like Jetstream, the `current_password` input is used.
I believe that adding `current_password` to the `$dontFlash` list by default would help to ensure new projects follow security best practices from the get-go.
* Update Handler.php
Co-authored-by: Taylor Otwell <taylor@laravel.com>
Docker allows for you to override parts of `docker-compose.yml` locally with the help of a `docker-compose.override.yml` file: https://docs.docker.com/compose/extends/#understanding-multiple-compose-files
I propose to have this file ignored by default for new projects, similarly to how `.env` is ignored to be able to override default configuration (locally).
Example use case: Someone might want to use Laravel Sail, but would have multiple Laravel projects running in MySQL and would like to run a single MySQL server for each project and have a way to be able to override docker-compose to make that happen. Or maybe just in general they want to add a new service that they want to run only for themselves, and not for colleagues.
