dinghy-http-proxy
dinghy-http-proxy copied to clipboard
codekitchen
the http proxy container that dinghy uses
I have a http container running on port 80. dinghy is used to make container available via https://my.domain.tld.docker on my development machine. So far so good. No I should run...
When dealing with authenticated cross domain requests, we can’t use wilcard for Access-Control-Allow-Headers. In that case we need to be specific about domains we want to allow. [This pull request](https://github.com/codekitchen/dinghy-http-proxy/pull/62)...
The jwilder proxy has recently added support for VIRTUAL_PATH to allow sub-path routing. It would be hugely useful for my team if that support was added to the codekitchen proxy.
The "CORS_ENABLED" variable gets defined as true if any container has the environmental variable set.
I just noticed that the container doesn't actually export port 443. You can still forward it, of course, but that's needlessly confusing.
I ran this on mac: ``` docker run -d --restart=always \ > -v /var/run/docker.sock:/tmp/docker.sock:ro \ > -v ~/.dinghy/certs:/etc/nginx/certs \ > -p 80:80 -p 443:443 -p 19322:19322/udp \ > -e DNS_IP=127.0.0.1...
Hi, I switched from `dinghy` to Docker on mac and use now your very good proxy / dns container. While it's working well from host to container, I a unable...
Hello, I'm trying out dinghy because regular ol' docker for mac is slow as molasses with large bind mounts. My stack consists of several `docker stack deploy` on a docker...
It would be great if the container would respect the `hsts=off` ENV var as the jwilder container does.
Hi All, I have been facing a strange issue with mounting volumes using the following command: ```docker run -d --restart=always -v /var/run/docker.sock:/tmp/docker.sock:ro -v ~/.dinghy/certs:/etc/nginx/certs -p 80:80 -p 443:443 -p 19322:19322/udp...
