title: How can I get apps in a docker network to talk with apps outside
body: <p>I have a situation where a system is made of quite a few clients and servers, all talking with each other.</p>
  
  <p>It was developed locally with each server listening on a different port.</p>
  
  <p>Now is time to put this in production, with an important fact: apps may be shuffled around and sometimes will live on the same computer and sometimes not.</p>
  
  <p>The only solution that made sense at this stage is to have each app be addressed by its name and use a reverse proxy on each machine.</p>
  
  <p>So, if there are x computers and each of them has a reverse proxy, some of the tools, and the dns is properly setup, it will all work.</p>
  
  <p>Where it will start to break down is when debugging comes into play:
  I still need to simulate the whole environment locally at times, with docker.
  And if I have a server running locally in the debugger, I can't find a good solution for the services running in docker to talk to it.</p>
  
  <p>One option would be to also have a reverse proxy on the local machine, but this is going to turn into hell very quickly.</p>
  
  <p>Has anyone faced that problem before and came up with a good solution?</p>