ytti

@FlorianDoublet I believe you wrote this? Want to refactor the posts which do not support JSON?

no worries, thanks.

Or perhaps it should have access levels, so that not everyone can pull node information.

On ruby 2.0 or older, or 1.9.3 with appropriate gem loaded it's all syslog, so we don't know where it's written, it might not be written even locally. We'd need...

Should we allow enabling both or just one at a time? log: syslog: true file: /tmp/poop or log: /tmp/poop syslog: true or log: [/tmp/poop SYSLOG]

Yeah we need to return file logging support. Especially for dockerized installs it's more prudent to log to file (STDOUT).

+1 thanks for this, very interesting stuff

I'd really appreciate some help here. I'd really like to avoid fetching the data from repo first, and I'd rather purge the trash/garbage, rather than leak it.

Bump

Have I presented my question poorly? Should I try to rephrase? Is there something I can do to help libgit2/rugged people help me?