Redirect requests on web_extra_exposed_ports to novarnish.DDEV_PROJECT.DDEV_TLD

[jedubois]

Let's say a user wants to run an additional service, e.g. KasmVNC, in their web container for some reason, and expose it on port 8444. With this add-on replacing the web container at https://DDEV_PROJECT.DDEV_TLD:8444 the URL provided in ddev describe would not work. Instead the user would need know/remember to go to https://novarnish.DDEV_PROJECT.DDEV_TLD:8444. We've got a solution in place for mailpit on port 8025 where Varnish listens on that port and redirects in the default,.vcl. I don't think that would scale to an arbitrary number of ports though. I think it would be great it we could do something more general either automatically or provide some documentation on how to approach it.

I've just run into this issue myself so have not got a solution to suggest yet. Perhaps we can have something very simple listen on the web_extra_exposed_ports if that can be read or some ports specified in .ddev/docker-compose.varnish_extras.yaml on the Varnish container and just do redirects.

[rfay]

It sounds like you're making a feature request. Now that you've thought about it a bit, could you edit it to make it very specific, step-by-step? And update the title to match your specific feature request?

I'm sure you're already thinking about how to do a PR, thanks.

[jedubois]

Yep, it's a feature request. I'll tidy it up in due course just wanted to get something out of my head before I had to move on to my next task. I've added the 'question' label to indicate this ticket needs fleshing out and assigned to myself. I'll have a rummage around for feature request format/guidelines when I get back to it.

[dlopez-akalam]

I'm having the same issue. There's a workaround for redirecting mailpit requests to novarnish.* url (#10). However, that solution doesn't work for internal network requests, for example http://web:8025/api/v1/messages. It doesn't work neither out of the box with other services making use of the web service, like tyler36/ddev-storybook for example.
Instead of redirecting, would be nice to work at traefik level, and route to varnish only the requests coming from the port 80 and 443, and route other ports directly to the web service.

[rfay]

A short-term note: You might consider using http://<hostname>.ddev.site:8025/api/v1/messages and see if it helps

That directs the traffic via the router.

[dlopez-akalam]

I've finally managed to solve it by using a different hostname for varnish, and keeping the webserver with its original hostiname. To do so, I've removed the docker-compose.varnish_extras.yaml and the changed the hostname on the docker-compose.varnish.yaml:

- VIRTUAL_HOST=varnish.${DDEV_PROJECT}.${DDEV_TLD}
- HTTP_EXPOSE=${DDEV_ROUTER_HTTP_PORT}:80

[stasadev]

Instead of redirecting, would be nice to work at traefik level, and route to varnish only the requests coming from the port 80 and 443, and route other ports directly to the web service.

@dlopez-akalam, I implemented this in:

• feat: use Varnish only for web:80, remove novarnish subdomains, fixes #32 #46