Output trace to STDOUT

[boldhedgehog]

Hi,

I'm trying baler in a Docker container, and I have infinite spinner with the message (Magento/luma) Create core bundle file. It looks like the baler does not do anything, and I want to enable a verbose mode or tracing.

This can be done with --trace CLI argument; however, the filename is generated based on current datetime, and I'd like to be able to specify the trace file name. In my case it's /dev/stdout.

Please add a parameter with the trace filename.

[jhruehl]

Had the same problem, but after pulling the latest version it works again.

[DrewML]

Hadn't considered this case - thanks for bringing it up @boldhedgehog!

I try to avoid adding options/configuration wherever possible. Would it work for you if we wrote the logs to a predictable filename (always baler-log.txt or something) so that you can tail -F the file?

Or is there a strong case to be made for being able to pipe directly from this binary to stdout?

[boldhedgehog]

A static file name is fine, I can create a symlink which points to /dev/stdout or /dev/stderr and hopefully anything going into the file will be "redirected" to the console output.