Anders

Here's a quickfix to emulate this behavior through ansible. It needs to be run in a role with `gather_facts: no` (and also before any other roles that do require facts):...

@Zyrophr, add a `/` to the end of your `location /flood {` like so `location /flood/ {`, do the same for your `proxy_pass` like so `proxy_pass http://127.0.0.1:3000/`, and then kill...

@billimek, I am almost certain that the hanging has something to do with the TCP connection not staying open via keep-alive so that flood can push the activity-stream data. I...

@DotEfekts I figured it out! On nginx when chaining 2 nginx reverse-proxies I can get keep-alives working by disabling proxy buffering on the front-facing proxy. It has no effect when...

@binarykitchen Still maintained. I fix bugs and stuff. Implementing new features though is just something that I take my sweet time doing. I have a plan for how to do...

All totally valid concerns. I should probably add a disclaimer to the readme stating something like I explained above. Regarding security concerns, I think you're OK. homeshick itself doesn't really...

This would be super useful in securing access to a Kubernetes cluster when combined with kube-apiserver X.509 client certificates (`--client-ca-file`). The apiserver accepts whatever the CN of a cert says...

@Jamstah done. @milosgajdos, I understand the issue. I mean, we could just replicate the entire struct I guess? In practice the options struct [seems to be quite stable](https://github.com/redis/go-redis/blame/master/universal.go#L12) and well...

Also, it looks like `redis.tls.enabled` had no effect previously? I don't see it used anywhere...

@milosgajdos, replicating the struct actually fixes the marshalling sooo :man_shrugging: fixed :-D