5.6 solution https://github.com/laravel/framework/pull/23439
Might just make it worth upgrading
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
On an Ubuntu production server, I have created a sudo'ers account that I log in with. Apache uses the usual www-data account.
If I deploy a new version of my application, and then some activity occurs that creates the log file, then the file is permission 644 and owned by www-data/www-data
My user is in the www-data group but the permissions explicitly exclude group write to the log file.
If I run an artisan command which includes Log statements then the command fails because my user cannot write to the log file.
How can I get Laravel to create the log file with group access so that my user can write to it.
Yes, I can chmod the log file (if it exists) but this is an unwanted complication.
Note that I also have the opposite issue. If the log file is not present and I run the artisan command that causes the log to be created, then now the file is owned by mark and cannot be written to by the framework.
Please or to participate in this conversation.