$ articles --topic=sre
SRE & Incidents
14 Laravel articles about SRE & Incidents.
Chainguard Broke the php2shell EmbargoChainguard CEO Dan Lorenc defends shipping fixed PHP builds before the embargo lifted on two critical remote code execution bugs, citing reports of exploits in the wild. PHP Foundation board member Nils Adermann disputes those reports and says Chainguard acted without telling the PHP team. The article also gives an opinion piece arguing the early release was a bad call.PHP · via PHP News · 16d ago5 minAn Example App That Needs Its FeaturesThe article describes Flagpole, a feature flag service built on the kit framework, and explains how its HTTP features were driven by the needs of the domain. It also covers four bugs in kit that the framework's own tests missed and that surfaced while building Flagpole.APIs · via juststeveking.com · 18d ago1 minWhen Retries Make Things Worse: Protecting Your System From OverloadLearn how a slow dependency can turn into a full outage when retries pile up, and how deadlines, concurrency limits, retry budgets, and jitter keep useful work flowing. The article includes PHP examples and a design for testing overload in a controlled way.PHP · via freek.dev · 19d ago1 minHow to Write Specs, RFCs and ADRsLearn what an RFC, an ADR and a spec are each for and how they differ in practice. The article shares the templates the author uses and walks through one feature from a blank page through all three documents.SRE & Incidents · via juststeveking.com · 1mo ago1 minPreview environments and scale to zero: Better togetherLearn how to give each pull request its own preview environment on Laravel Cloud, so you can share a link and test the full stack. Also see how idle previews can scale to zero to keep costs down.Laravel · via blog.laravel.com · 1mo ago1 minSetting up a remote environment for agentic codingThe author explains why running coding agents on a laptop became a bottleneck and walks through setting up a remote development environment for agentic coding. Expect the reasoning behind the move and the practical steps to get it working.SRE & Incidents · via ma.ttias.be · 3mo ago1 minWhat 1.8 million real website outages look likeOh Dear, a service that monitors websites, shares what its data on about 1.8 million real website outages shows. The piece looks at the patterns and causes behind downtime as seen across a large set of real incidents.SRE & Incidents · via ma.ttias.be · 4mo ago1 minDependency HygieneA post on dependency hygiene, the habits that keep a project's third-party packages maintainable and secure over time. It covers how to think about which dependencies to add, keep current, and remove when they are no longer needed.Git · via stitcher.io · 7mo ago1 minBlocking SessionReaper and PolyShell File Access with Fastly on Magento/Adobe CommerceShows how to block direct requests to the media/custom_options/ directory at the Fastly edge with a short VCL snippet, stopping SessionReaper and PolyShell payloads before they reach the origin. Also covers the trade-off for stores that use file upload custom options.APIs · via dor.ky · 7mo ago3 minNginx client_header_buffer_size - Debugging Cloudflare-related 400 Errors for Magento/Adobe Commerce HTTP RequestsA developer traces mysterious 400 errors on Magento webhook POSTs routed through Cloudflare and Nginx, finding the cause was too-small client_header_buffer_size and large_client_header_buffers values. Increasing them fixed the problem, and the post shares a tip to isolate which layer throws the 400.SRE & Incidents · via dor.ky · 10mo ago3 minFlush Fastly CDN via CLI/Command Line for Adobe Commerce ProjectsLearn how to purge the entire Fastly CDN cache from the command line with a single curl request when the Adobe Commerce admin panel is unavailable. The post also explains where to find your Fastly API key and service ID on a Commerce Cloud cluster.AWS · via dor.ky · 11mo ago1 minHow to Strangle your Project with Strangle Anti-PatternThe article explains why the strangle pattern, a common approach to incrementally upgrading a codebase one section at a time, often backfires in practice. It describes how teams end up running two frameworks and doubling their complexity, and it introduces a better upgrade strategy to use instead.SRE & Incidents · via Rector · 1y ago1 min