Skip to content

Conversation

@flanker
Copy link

@flanker flanker commented Aug 15, 2015

  • e.g. Services running in Docker containers on Mac OS X need to be accessed via
    Docker VM IP address instead of OS X's localhost.

On Mac OS X, dockerized services are not running as localhost. They need to be accessed via Docker VM (boot2docker or Docker machine) which usually has a different IP (e.g. 192.168.59.103)

Added this cli option to specify the backend service host. So the proxy could find the correct backend service.

…ning locally.

* e.g. Services running in Docker containers on Mac OS X need to be accessed via
Docker VM IP address instead of OS X's localhost.
@iffyuva
Copy link
Member

iffyuva commented Oct 12, 2015

@flanker thanks for the PR. this looks good to me, but i have a concern: since backend_host is no longer under invokers' control to check if invoker setup has been run properly or not, i suspect this will create more problems. @gnufied @nisanth074 what do you guys think?

@gnufied
Copy link
Contributor

gnufied commented Jan 20, 2016

This makes ton of sense. @flanker I just merged https://github.com/code-mancers/invoker/pull/146/files which implements this partly.

Can you update this branch with latest master? I will be happy to look and merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants