ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #php
I am designing a caching layer on top of laminas-cache (current 3.x line, using the Redis storage adapter) for values that are expensive to regenerate and read very frequently. Each entry gets a TTL, and once it expires every reading process sees a miss at roughly the same time. From the documentation I can see TTL handling, getItem metadata, and TaggableInt
For instance, Symfony's configuring-environment-variables-in-env-files documents provides examples: DATABASE_URL="mysql://db_user:db_password@127.0.0.1:3306/db_name" DB_USER=root Why are quotes (aka parentheses) used for the first example and not the second? If the applicable answer is dependent upon the application parsing the .env file, please base it on S
Goal: Verify the exact offset PHP selects when a DateTime representing an ambiguous local time (e.g., 01:30 am during a fall‑back transition) is converted with setTimezone to a zone that observes the same offset, and whether the result is consistently the earlier offset. Constraint: This behavior is not documented as a rule and may vary with timelib updates;
In long-running PHP processes, such as worker scripts or daemons, memory consumption may increase over time despite the use of reference counting. While PHP employs a cycle collector to handle circular references, the timing and efficiency of this reclamation can impact stability when scripts operate near the memory_limit threshold. There is a trade-off betw
Goal Present timestamps from the database in a user’s local time zone, honoring daylight‑saving transitions without manual manipulation. Current Constraints The CI Date helper delegates to PHP’s native date() and DateTime , which rely on the PHP default timezone unless the framework’s timezone config is set. The helper’s now() returns a timestamp in that con
Livewire public property exposure In Livewire, any property declared as public on a component class is automatically serialized and sent to the browser. If a developer inadvertently marks a sensitive value—such as a user ID, API token, or an Eloquent model—as public, that data becomes available to any client that can trigger the component. There is no built‑
CodeIgniter 4 utilizes a driver-based caching system relying on Time-To-Live (TTL) for data expiration. While the framework supports various backends such as Redis, Memcached, and File, it lacks a native mechanism for tag-based invalidation or group cache clearing. When underlying database records are updated, the associated cache entries remain stale until
Problem On Sulu 2.5 (Symfony 6.x), a full rebuild of the search index via bin/websiteconsole sulu:search:index (or the admin reindex action) is terminated partway through large content trees. The process appears to be stopped by PHP's max_execution_time rather than by any Sulu-level timeout, and no partial-progress or cancellation message is surfaced in the
I am processing a large result set in a long-running PHP CLI job using Doctrine ORM. Memory usage climbs steadily as the loop iterates, which I understand is the UnitOfWork identity map retaining every managed entity. The documented mitigation is periodic flush() followed by EntityManager::clear() , but I am unsure how to apply it safely in my case. My loop
laminas
symfony
codeigniter
livewire
laravel
redis
doctrine