Replies: 5 comments 5 replies
-
WorkaroundIf your laravel deployment with docker is doing things the
|
Beta Was this translation helpful? Give feedback.
-
Totally agree with the proposal. Current implementation breaks 12-factor methodology. |
Beta Was this translation helpful? Give feedback.
-
Previously that issue was mentioned in #38429 Also, one of the solutions is to extend comand description like $schedule->command(TestLogCommand::class)->everyMinute()->thenWithOutput(function (Stringable $output) {
echo $output;
}); |
Beta Was this translation helpful? Give feedback.
-
This is a challenge to understand when deploying to k8s - my
becomes
so Datadog and K8s have no way to get the command's logs. |
Beta Was this translation helpful? Give feedback.
-
Run in background scheduled task is not compatible with stdout logging in laravel. See #50085 (comment) |
Beta Was this translation helpful? Give feedback.
-
Laravel Version
9.29.0
PHP Version
8.1.20
Database Driver & Version
No response
Description
Scheduled Tasks seem to force output to /dev/null unless a local disk file is provided to write output to.
On Docker-based or similar deploy-code / spin-up-instances hosting services like heroku.com or fly.io etc. local files are usually ephemeral and thus local log files are quite useless.
These hosts usually offer a live scrolling app output console log that can be monitored, very useful to catch live exceptions or view logged notices/warnings etc.
It would seem very desirable and necessary to have the option to let
schedule:run
allow laravel Schedule Events' output to proceed on to STDOUT along with all other app output. Suppressing it to /dev/null with no option to allow it through to STDOUT seems like blocking useful options for many deployment environments.Steps To Reproduce
->line()
or->table()
or whatnotSome relevant links
Beta Was this translation helpful? Give feedback.
All reactions