Thanks @Gazler for your responses. I’m adding a +1 here because I’ve been trying to achieve the same result. My use case is that I want to build multiple apps, imagine a portfolio of sample projects or maybe micro-services, but as a developer I don’t want to create a new Digital Ocean droplet or AWS server or new Heroku app or dockerfile for each app. I want each App to almost be like a package in bigger App. Do you get what I mean? Do you have another way of achieving this? Most tutorials or application demos assume that they’re either monolithic or the only thing running on the server so they default to binding to port 80/443 etc. or default application entry point. Imagine a hosted app with ports in the domain name like google.com/gmail:4567 most people just want to see gmail.google.com and the port routing is handled somewhere… bonus points to Alphabet because even gmail.com works too. 
Why can’t we have multiple apps running on the same server at different ports and being routed internally on the network or app layer through nginx or plug? I’ve tried a few different solutions but I can’t seem to have assets, websockets and APIs all working at the same time. Using plug and the host value to route requests still means that the assets aren’t delivered add plug proxy for holaWeb.Endpoint · iampeterbanjo/hello-proxy@a00b684 · GitHub and using Nginx means that the websocket requests don’t work hello-proxy/nginx/nginx.conf at master · iampeterbanjo/hello-proxy · GitHub
With Elixir umbrella projects it seems that we are so close to making this work… so close 
