Heath Naylor

Just a follow up, this looks to be fixed as of tag 1.9.

@brianmc Can we please have some response or understanding if this will get merged in at some point? Maintaining our own fork is less than ideal.

Thank you for the reply, happy to see progress on this issue. 1) Firstly, the goal of logger injection is testability and flexibility, . Right now you have a `LogFactory`,...

Yup, I am aware of that. It is not _ideal_ as a singleton though, in case for different requests I would want different log levels. I will rename this issue...

@gnongsie is there plans for this to become a feature and merged into a release?

Ahh, the beauty of open source. Your fork works great.

If we want to use PHP 7, we need to use the 0.x tags?

I am having forky max memory and swap as well, it just creates more and more threads that take a memory chunk until the server crashes.

@marclar I just pulled out the Forky layer and spanned the application across multiple nodes with the database decoupled. Sorry it isn't a true solution but it solves the problem...

I just have the same application running on several servers with a load balancer distributing load across them. If I were writing a nodejs application from scratch I might look...