On Thu, Jun 27, 2019 at 4:24 PM Eric Covener wrote:
> > From my perspective it would be advantageous to have Apache write to
> > the terminal by default (i.e. no hardcoded log file locations) and
> > allow to override this behavior via the Apache configuration file.
>
> > Is there any reason why
On 06/27/2019 11:53 PM, Alex Hautequest wrote:
> $ tail -F /var/log/apache/access_log /var/log/apache/error_log
>
> There’s your stdout output, no code modifications needed. You are welcome.
>
> Jokes aside, you could make use of a web socket to pull these logs out in a
> way code doesn’t need to
$ tail -F /var/log/apache/access_log /var/log/apache/error_log
There’s your stdout output, no code modifications needed. You are welcome.
Jokes aside, you could make use of a web socket to pull these logs out in a way
code doesn’t need to be changed. Or you could dump them straight into a
> From my perspective it would be advantageous to have Apache write to
> the terminal by default (i.e. no hardcoded log file locations) and
> allow to override this behavior via the Apache configuration file.
> Is there any reason why the default behavior is not that way yet?
I think it's useful
Hi there!
In my day job I'm helping to get applications from traditional
environments running in cloud environments. Cloud native applications
are just "normal" applications, but there are a few properties that
they should satisfy (apart from resiliency and scalability).
For logging this boils
