Openshift - Configure logging to not write in a file

Because it requires specific permission in the CWD. Ideally, this can be passed in the command line:

./app -Dlogfile=none

or something like that.

[vorburger]

@geoand yup, and I have proposed that in #1599 if that’s the conclusion of this issue’s discussion…

… but I personally actually do also think that this is the wrong approach - the default of true of quarkus.log.file.enable seems wrong, to me, for a “Kubernetes Native Java stack” framework… IMHO default should be console, only; and log file should be opt-in (12 Factor).

-Dshamrock.log.file.enable=false

BTW: It’s quarkus.log.file.enable and not shamrock.log.file.enable, right?? That’s what doc’d.

[cescoffier]

I agree, we may change the default, and allow writing to file when the user wants it.

On Thu 20 Dec 2018 at 10:01, Georgios Andrianakis [e-mail] wrote:

Since Protean is meant to be container first, wouldn’t it make sense to not write to a file by default?

I mean one of the factors of the 12 factor app design is to log to stdout only.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jbossas/protean-shamrock/issues/355#issuecomment-448923669, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYjff2MZNRrKSX0lXoENWrKJznMBwetks5u61HwgaJpZM4ZbsIP .