Webdeveloper & Co-founder of Fruitcake
The Netherlands
Joined November 2009
- Tweets3.2K
- Following504
- Followers10.7K
- Likes1.7K
Tip for managing multiple AI agents / projects / worktrees: onorca.dev/
Keeps your agents, terminals and code viewer neatly grouped per feature and makes it clear which agents needs your attention 👌
My preferred setup is creating a .env.testing file where we just change the database name (and other creds) + a phpunit bootstrap script that exits when the file doesn't exist.
- Same database type
- No left-over data
- AI agent can just refresh the data (uses --env=testing)
Barry vd. Heuvel retweeted
v1.1.0 of LaraDocs just released!
Massive thanks to @barryvdh who contributed most changes to this version!
View the changelog 👇
laradocs.dev/docs/changelog
Did you know that your AI can debug your requests using Laravel Debugbar?
No MCP server required, works directly with Laravel Boost. And without Boost, you can use the new `php artisan debugbar:install-skill` command to install the skill directly!
See github.com/fruitcake/laravel…
I've built something similar to generate dynamic images (like Glide), but cache them as static images.
Benefits:
- Dynamic formats and presets
- Generated on the fly from a Disk
- Secure (using signature)
- Stored as plain images (only hit PHP once)
github.com/fruitcake/laravel…
Laravel Image Responses: Serve Resized Images From Routes posted by @paulredmond laravel-news.com/laravel-ima…
The laravel/ai SDK is great! And in the latest Laravel Debugbar release, we added an AI tab to show the instructions/tools/response etc! We've also added an (experimental) way to capture streaming responses in Debugbar directly when they are done. See laraveldebugbar.com/usage/#s…
PHP developers used to have limited options for building AI agents: learn Python, or accept that raw API calls were as far as you'd get.
The Laravel AI SDK changed that.
Agents, tools, memory, streaming, vector search, and multi-agent workflows. All in Laravel, and all first-party.
Learn more about the AI SDK →
laravel.com/blog/building-ai…
Small improvement in the latest laravel-debugbar; it automatically detects the nonce from either Spatie laravel-csp or the Vite::useNonce(), so you no longer have to manually set them. Makes it easier to set stricter CSP while developing locally with Debugbar enabled.
Just added some instructions to the readme of laravel-csp on how you can use the nonce generated by @laravelphp’s Vite plugin
github.com/spatie/laravel-cs…
👏 @timacdonald87 for his nice work on the plugin
#laravel #php
Check your Github Actions to make sure you're not using a pinned/old Composer version, and set the Github Tokens to Read instead of Read+write: github.com/composer/composer…
A version is tagged and it seems like shivammathur/setup-php is installing that already. But still watch out!
Performance improvement in Debugbar: replaced HtmlDumper with a new JsonDumper that stores pure JSON + a custom JS renderer.
This gives up to 20x speed and 15x size improvement 🔥
Bonus: lazy rendering to reduce front-end impact and added inline previews for a compacter view!
I added a @laravelphp Boost skill + cli to Laravel Debugbar to help you fix issues and optimize queries 🤖
It can:
- Browse latest requests
- See collected data and show details
- Show overview of queries (with duplicates)
- Query details (backtrace and even EXPLAIN results)
Give it a try by updating to the latest release (github.com/fruitcake/laravel…) and just run `php artisan boost:install` to install the Debugbar skill
Small new Laravel Debugbar feature: Re-run SELECT queries to help debug your results (opt-in via config)
You probably know you can use the Explain feature to find missing indexes, but now you can re-run the entire query and render it as a table or dump result, or expand it.
Barry vd. Heuvel retweeted
Bij Fruitcake vinden we het belangrijk om te investeren in Open Source, mede door het maken van gratis tools. Barry maakte in 2013 de alom bekende Laravel Debugbar. 12 jaar later is versie 4.0 gereleased!
Benieuwd wat die Debugbar doet of wat nieuw is? Check onderstaande blog!
I released Laravel Debugbar 4.0!
Check the release blog: fruitcake.nl/blog/laravel-de…
This brings a lot of changes under the hood (like php-debugbar 3, no jquery, optimized loading) but also a lot of Laravel improvements (better Livewire/Inertia/Octane support) and more collectors!
I released Laravel Debugbar 4.0!
Check the release blog: fruitcake.nl/blog/laravel-de…
This brings a lot of changes under the hood (like php-debugbar 3, no jquery, optimized loading) but also a lot of Laravel improvements (better Livewire/Inertia/Octane support) and more collectors!
I released a new major version of PHP DebugBar.
- Removed jQuery and FontAwesome -> much smaller size
- Optimized rendering for heavy tabs
- New widget for ajax/stacked requests
- Typehints, build scripts, static analysis and much more!
For details: github.com/php-debugbar/php-…
This Livewire RCE (>=3; < 3.6.4) is now actively being abused with an exploit available;
securityonline.info/critical…
Hearing reports of:
- new php files in public folder with backdoors
- perl scripts active processes
- weird jobs in the queue
Check your version and update!
Don't forget to update Livewire 3 as soon as possible! Not sure what the issue is exactly, but you probably want to have this security update live before it's public knowledge; github.com/advisories/GHSA-2…
Detailed report: synacktiv.com/en/publication…
Exploit: github.com/synacktiv/Livepyr…
Given how easy this exploit is, and how widespread the attack; if you didn't update before Dec 23rd you should assume your .env is leaked and rotate your keys, regenerate APP_KEY and replace your server..
To be super clear; if you're running Filament with an outdated Livewire; you are still affected, even if you're not using any Livewire code in the front-end.
The articles demonstrates this with the default Filament login form (so unauthenticated): synacktiv.com/en/publication…