it is madness
it is madness
I agree that we should definitely write up a CONTRIBUTING.md that lays out style guides (especially as the style in app/ is going to be different than the legacy code...
This is our only public Git location, we just hadn't pushed from our internal git to here, but did it just now.
So in looking to implement this within a logchecker for Orpheus, one of the biggest hurdles I think we face is just knowing what are the possible logs that whipper...
Sorry for having this closed, we had to do a force push due an internal hiccup we had. I've created #192 to track merging this PR.
This was implemented.
What a poor change as it really complicates the record keeping. It reads to me that to follow BEP-007, we can now expect a user may send the same announce...
Two test logs that I've seen affected by this: [cs_1250.log](https://github.com/ligh7s/hey-bro-check-log/files/4481807/cs_1250.log) [pl_1250.log](https://github.com/ligh7s/hey-bro-check-log/files/4481810/pl_1250.log)
Hi @blobb3r, this is most likely due to bad permissions on `cache/twig/`. Could you double check what they are? You should also ideally be able to see an error log...
`/var/log/php/` is a directory that should have an `error.log` file.
Per user. It should be done similarly to how `track_ipv6` was added in that it will be a column in the database for users table that ocelot will pull in...