Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update links now that example is in master #62

Merged
merged 2 commits into from
Sep 12, 2016
Merged

Update links now that example is in master #62

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a95dd83
Update links now that example is in master
junr03 Sep 12, 2016
90838b3
Change to :repo:
junr03 Sep 12, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 3 additions & 6 deletions docs/install/sandboxes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,14 +16,11 @@ Below you can see a graphic showing the docker compose deployment:

All incoming requests are routed via the front envoy, which is acting as a reverse proxy sitting on
the edge of the ``envoymesh`` network. Port ``80`` is mapped to port ``8000`` by docker compose
(see `docker-compose.yml
<https://github.com/lyft/envoy/blob/docker-example/example/docker-compose.yml>`_). Moreover, notice
(see :repo:`/example/docker-compose.yml>`). Moreover, notice
that all traffic routed by the front envoy to the service containers is actually routed to the
service envoys (routes setup in `front-envoy.json
<https://github.com/lyft/envoy/blob/docker-example/example/front-envoy.json>`_). In turn the service
service envoys (routes setup in :repo:`/example/front-envoy.json>`). In turn the service
envoys route the request to the flask app via the loopback address (routes setup in
`service-envoy.json
<https://github.com/lyft/envoy/blob/docker-example/example/service-envoy.json>`_). This setup
:repo:`/example/service-envoy.json>`). This setup
illustrates the advantage of running service envoys collocated with your services: all requests are
handled by the service envoy, and efficiently routed to your services.

Expand Down