The Slack log channel username falls back to the generic "Laravel Log"
when unset. This updates the fallback to use `APP_NAME` instead,
making it easier to identify which application is sending logs when
multiple Laravel apps post to the same Slack channel.
Follows the same pattern as #6755 which added an `APP_NAME` fallback
in the mail config.
The `MAIL_FROM_NAME` config value falls back to the generic "Example"
when unset. This updates the fallback to use `APP_NAME` instead,
matching the convention in `.env.example` where `MAIL_FROM_NAME`
references `${APP_NAME}`.
* Ignore Laravel compiled views for Vite
Before testing, run php artisan cache:clear to clear old compiled views.
This issue only happens during local development when running npm run dev.
Laravel continuously recompiles Blade into PHP inside storage/framework/views (especially after Livewire re-renders), and these files are changed by Laravel itself, not by us.
Because of that, Vite thinks we modified a file and triggers a full reload—even though the change is purely internal framework logic. This makes the reload behavior unacceptable and noisy during development.
Since these compiled views belong to Laravel’s backend logic and not frontend assets, Vite does not need to watch them.
Ignoring storage/framework/views keeps Vite stable and prevents reloads caused by Laravel doing its own internal work.
* Vite ignore rule now in one clean line
* Replace Bootcamp with Laravel Learn
* Revise text for Laravel Learn section
Updated wording for Laravel Learn link in README.
* Update Laravel learning resources in README
Removed redundancy in Laravel learning resources and added a link to Laravel Learn for guided application building.
---------
Co-authored-by: Taylor Otwell <[email protected]>
Taylor Otwell