Closed mcollina closed 8 years ago
2 x Yes, docker-loghose looks pretty stable.
We use docker-loghose in production for Sematext Agent Docker - and we have to switch over to local repositories in case of hot fixes for our docker image ... so helping out here could save us some time.
@megastef I've add you as a collaborator.
Any other opinion on the matter?
Hi, sounds good to me! Cheers On Feb 4, 2016 4:58 PM, "Matteo Collina" notifications@github.com wrote:
@megastef https://github.com/megastef I've add you as a collaborator.
Any other opinion on the matter?
— Reply to this email directly or view it on GitHub https://github.com/mcollina/docker-loghose/issues/8#issuecomment-179945262 .
Solved by https://github.com/mcollina/docker-loghose/pull/10 In addtion a bit of tuning: https://github.com/mcollina/docker-loghose/commit/68d87bcebe1c4f5d35f043b0006dcbda39b1cac9 Buffer.byteLength() is ~3 times faster then new Buffer().length and reduces memory usage and garbage collection.
Finally the README got a working example and latest format specifications https://github.com/mcollina/docker-loghose/commit/a9acf5b7e740435d3565fc154babb54be5183b14
Released 1.0.0
Should we graduate docker-loghose to v1.0.0? It seem quite stable.
cc @megastef @cammellos
also @megastef would you like to become a collaborator here?