ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #symfony
The goal is to decide whether enabling the DoctrineBundle persistent option (which sets PDO::ATTR_PERSISTENT ) is advisable when running Symfony under PHP‑FPM, weighing the benefit of reduced connection churn against the risk of exhausting the database’s max_connections due to each PHP‑FPM worker maintaining its own persistent connection. Constraints include
Context Symfony HttpClient executes upstream calls with its own timeout configuration ( timeout , max_duration , stream timeout) that operates independently of the enclosing HTTP request lifecycle. When a client disconnects early—closing the browser tab, cancelling a fetch, or hitting a reverse-proxy timeout—the inbound Symfony request terminates, but the ou
Accessibility Gap in Default Form Error Rendering Symfony 6.x renders form error messages through form_row() and form_errors() Twig functions without automatically including ARIA live region attributes. This creates a potential accessibility barrier where screen readers may not announce validation errors when they appear dynamically during form submission. S
Managing Alert Volume in Asynchronous Processing The Symfony Messenger component allows for the configuration of a RetryStrategyInterface to handle transient failures via max_retries and exponential backoff. While routing permanently failed messages to a failure_transport prevents infinite loops, it introduces a challenge in balancing alert sensitivity with