Sabitlenmiş Tweet
Every @laravelphp MCP tutorial ends at a weather example.
What they skip: auth trade-offs, tool scoping, and the NeighborJack vulnerability hitting hundreds of exposed servers.
The production guide I wish existed 👇
English
Mozex
83 posts
Mozex
@mozexdev
Senior Laravel Specialist · 10+ years · Building open-source PHP packages for thousands of developers · Available for consulting
Istanbul, Turkey Katılım Kasım 2016
88 Takip Edilen15 Takipçiler
@enunomaduro @ThePrimeagen @theo Not a streamer but I constantly watch your streams after they're done at double the speed, so please keep them public 😁
English
.@theprimeagen @theo and really anyone who streams: what's the impact of keeping livestreams public on youtube? does it hurt the channel metrics-wise, or is it basically fine?
mine are public right now, but i tried making them private for 2 weeks and it felt like it hurt the channel’s watch time.. curious if anyone has actual data/thoughts on this
English
A client shipped a one-comma tweak to their @AnthropicAI system prompt and doubled their Claude API bill overnight. Prompt caching's invalidation rules are stricter than the docs make obvious. The @laravelphp pattern that holds up in production 👇
English
Every @laravelphp cron in production needs an external heartbeat. Yours probably doesn't have one. @OhDearApp catches what Laravel can't: "schedule:run hasn't pinged in 3 minutes, something broke."
The 5 failures behind the pattern 👇
English
Incredible News! I was really considering migrating to Mac just to use @getpolyscope
Marcel Pociot 🧪@marcelpociot
As it was so unnerving to watch I had to share it with you. You're welcome
English
Your @laravelphp queued jobs sometimes fail because they run before your transaction commits. Your tests never catch this. Same process, same DB connection. Production? Separate workers, separate connections.
The config line that fixes it 👇
English
@enunomaduro Heads up for anyone running a modular Laravel app
The new time-balanced sharding needs a small tweak to work correctly (same situation as the original Shard plugin). I wrote up the fix here: mozex.dev/blog/2-fixing-…
Happy to PR upstream if there's interest @enunomaduro 🙌
English
@enunomaduro Will do 🙌 might post the before/after once I run it through. Thanks Nuno!
English
@mozexdev Ask AI to split those slow test cases into various test files
English
Incredible feature 🔥 really needed this, thanks @enunomaduro
the shards were looking like this:
nunomaduro@enunomaduro
just released pest v4.6.0 with time-balanced sharding this was a long-time request from the @laravelphp cloud team; with around 15,000 tests, browser tests and other slow ones need to be spread evenly across all shards fucking dope
English
@enunomaduro Unfortunately since I am using a modular application, it doesn't work for me. I fixed Shard plugin for modular applications but for this new feature I have to work on it as well.
English
Mozex retweetledi
Fixing Pest Sharding for Modular Laravel Applications
mozex.dev/blog/2-fixing-…
#Laravel #PHP #Testing #Pest #GitHubActions
English
@freekmurze @timacdonald87 Love this. One ask, a marketplace/plugin for your skills repo would be 🔥. Copy-pasting means I miss every future tweak you make. An install + auto-update flow would be killer.
English
Created a skill with @timacdonald87 's tips
Feel free to grab it here: github.com/freekmurze/dot…
x.com/timacdonald87/…
#testing #php #laravel
Tim MacDonald@timacdonald87
@0x15f @enunomaduro @taylorotwell This is without knowing anything about your test suite or app, but a few thoughts off the top of my noggin. Realistically, I don't think there will be a quick solve here. My guess is item one will be the place to dig but also requires the most work.
English
Fat controllers aren't a style problem. They're the most reliable predictor of overall codebase quality I've found in 10 years of @laravelphp.
One grep command tells me more than reading code all day 👇
English
New tradition thread: 3 Upwork jobs for Laravel devs.
I also include PHP jobs, or projects with other/unspecified stack that are suitable for Laravel, so you may discuss with client.
Thinking: maybe turn it into DAILY EMAIL every morning?
Would you subscribe?
Thread below.
English
@danjharrin Until GitHub ships proper controls, a webhook that auto-closes issues/PRs not matching the template format works as a stopgap. Not ideal, but it filters out the lazy bypass attempts.
English
What even is the point of (mandated) issue templates on GitHub anymore if there are easy workarounds for third party contributors / their agents to bypass them 🤦♂️ submitting through the API, converting from a discussion...
No, I don't want your agent submitting issues and PRs 🤷♂️
English