Cannot ignore failure to load conf/app.conf because log writes to STDOUT about beego HOT 2 CLOSED

Currently we cannot ignore it. But i think it has no impact to live environment

from beego.

It's meant to be able to be ignored, because you might not use this config file. SInce it's logging to STDOUT though, my system cannot ignore this because it's printing the warning message into the output when executing my command line tool.

For example, I have a command line tool that utilizes the models and services that I have built in my Beego application, and when running it, should output a valid JSON object, but this is not possible, because the output to STDOUT is always something like:

2023/11/29 20:47:19.539 [D]  init global config instance failed. If you donot use this, just ignore it.  open conf/app.conf: no such file or directory
{"order_id":"12345"}

This should be sent instead to STDERR so that you aren't forced to include this in the output. I cannot override the logging here either.

from beego.