fixes logging of scheduled tasks

[aknosis]

Due to the way that Laravel executes scheduled tasks, coupled with bref sending everything to stderr (by default) logging inside of scheduled tasks end up in /dev/null.

In CloudWatch you will see commands run like so:

2024-07-26 18:44:10 Running ['artisan' example:command] ... 194ms DONE
--
⇂ '/opt/bin/php' 'artisan' example:command > '/dev/null' 2>&1

With this change you can now see logs:

2024-07-27 00:02:09 Running ['artisan' example:command] [2024-07-27 00:02:09] staging.DEBUG: first debug
--
[2024-07-27 00:02:09] staging.DEBUG: second debug
... 132ms DONE
⇂ '/opt/bin/php' 'artisan' example:command >> '/proc/1/fd/1' 2>&1

I didn't do any real in depth look into the availability of /proc/1/fd/1 but it would fail on my mac so I added the file_exists() check.

Can add tests if desired, hooking into this even seemed like the least intrusive way to accomplish this.

[mnapoli]

Thanks for reporting this, I'm surprised this is the first time we hear about it. But it seems that it also happens on Vapor: https://stackoverflow.com/questions/62485981/why-do-logs-that-are-run-by-schedulerun-on-laravel-vapor-not-saving-in-cloudwat

That would be great to solve this indeed 👍

[mnapoli]

Oh I just caught up with the Slack thread, that answers my question :)

Thanks a lot for investigating and solving this!