ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #lumen
Lumen leverages the Carbon library for date and time manipulation, with the default behavior governed by the app.timezone configuration value. While this setting dictates the offset for date generation within the application layer, the behavior changes when persisting these values to a database. A specific challenge arises when using database columns that do
Our team maintains an API built on Lumen, the Laravel-derived micro-framework, and we are standardizing repeatable development environments across machines. With Lumen no longer actively developed and the Laravel team recommending Laravel (optionally with Octane) for new work, we need to decide how to keep this project reproducible without taking on unplanne
Developers need to confirm that custom facades and service providers continue to operate after upgrading a Lumen application from version 8.x to 9.x, given the framework’s new PHP 8.0 minimum requirement. The shift removes support for PHP 7.x‑specific constructs such as the each() function and certain mb_ereg_* calls without explicit encoding, meaning any fa
Goal: verify that after executing Cache::tags('posts')->flush() the associated cached values are no longer returned, ensuring that stale reads do not occur. Constraints: the file driver may delay actual deletion due to OS page caching, while the Redis driver performs atomic tag removal but still depends on the timing of the flush relative to data updates.
carbon
composer
laravel