Hart Simha

Documenting the difference is certainly preferable to leaving it open to misinterpretation as an immediate measure :) As for what to do in v2, I'm not sure. `Read()` isn't in...

I suspect this is related to how the redis is configured through apt install on Ubuntu rather than the timeseries.so build. I have no problem running redis with the timeseries...

Thanks @chayim , actually got a newer version of redis sorted out, and also saw news of redis-stack, which looks exciting! I left this issue open as I was thinking...

I uninstalled node and reinstalled with apt: ``` curl -fsSL https://deb.nodesource.com/setup_16.x | sudo -E bash - sudo apt-get install -y nodejs ``` And was able to install bcrypt, so this...

vagrant-libvirt *will* create the libvirt network for you; what I've done (using KVM as the driver) is set `override.vm.network "public_network", dev: "br0, type: "bridge"`

> As for this, I think there is some confusion. The express-session middleware only relies on the value of req.protocol , which the "trust proxy" setting can be used to...

Hmm.. that makes sense. Perhaps the 'safe' thing to do would be to only look at the `Forwarded:` header when it's explicitly specified in an option where `proxy-addr` is being...

After comparing portus and docker hub's token servers' response headers to token requests which contained bad credentials, I realized that Portus's *token server* would send a `WWW-Authenticate: Basic realm="Application"` header...

I created https://github.com/HartS/Portus/commit/0a5b217b5e4cc42438dc99eea7e61047c2655eca, which sets the Devise `http_authentication_realm` from an environment variable. This is working for docker-compose deployments, but I could use some guidance about how to also handle this...

Hi, I just noticed the recent activity in my notifications. I haven't looked at Portus in a while and don't remember the details unfortunately > I wanted to also include...