Laravel Logs Rotate Laravel Package

Product Decisions This Supports

• Log hygiene automation: deciding whether to build in-house log rotation (cron + shell scripts) vs. adopt a configurable Laravel package — this release strengthens the "buy/adopt" case by adding a min size guard so tiny files aren't needlessly rotated.
• Roadmap for operational maturity: supports decisions to standardize log retention policies across services without writing custom retention code.
• Feature prioritization: the new minimum file size option enables use cases like "retain last N days but skip rotation if the file is under X KB," which helps when auditing storage costs vs. log completeness.
• Incident/debuggability decisions: teams can decide to keep small, low-volume logs intact longer (avoiding churn/empty rotations) while still capping large high-volume logs.
• Build vs. buy: reduces the need for bespoke log management scripts; relevant if your product runs on Laravel with filesystem-based logging.

When to Consider This Package

• You run Laravel (or a PHP app with Laravel's logging stack) and rely on daily/size-based log files on local or shared storage.
• You need policy-driven rotation (age, count, size) configured in code rather than via external logrotate/cron.
• New in 2.9.0: you want to avoid rotating small logs — set a minimum file size threshold so low-volume environments (dev, small tenants) don't generate needless rotated files.
• Look elsewhere if: you use centralized log aggregation (e.g., stdout → Fluentd/Loki/CloudWatch) where container logs are handled by the platform; you need OS-level logrotate guarantees; or you require multi-node coordination (this is a per-app filesystem concern).
• Evaluate if your team already has a robust external logging pipeline — duplication adds operational overhead.

How to Pitch It (Stakeholders)

Executives: A small, low-risk dependency that automates log cleanup for our Laravel services — reducing manual ops toil and storage bloat. The 2.9.0 update adds a sensible guard against rotating trivially small files, cutting noise and unnecessary churn.

Engineering: Adopt via Composer; configure retention (days/count/size) in config/logs-rotate.php. 2.9.0 introduces a minimum file size option (PR #47) so rotation only triggers above a threshold — useful for low-traffic environments and avoiding empty/no-op rotations. No breaking changes in this release; safe minor upgrade from 2.8.x. Recommend pinning and validating config in staging before rollout.