Sign inSign up

iheve/serf-reverse-proxy

By iheve

•Updated over 10 years ago

This docker container is an http nginx reverse-proxy. It uses serf to keep an up-to-date nginx configuration.

Image
2

1.7K

iheve/serf-reverse-proxy repository overview

⁠docker-serf-reverse-proxy

Code available at : https://github.com/Iheve/docker-serf-reverse-proxy⁠

Containers available at :

This docker container is an http nginx reverse-proxy. It uses serf to keep an up-to-date nginx configuration.

To build this docker, use docker build -t iheve/serf-reverse-proxy .

To run this docker, use docker run -d -p 80:80 iheve/serf-reverse-proxy

You will be able to browse http://localhost/⁠

⁠Architecture of the solution

Alt text

⁠Configuration update

Alt text

⁠Back end

You can find the base back-end image in the back-end folder.

⁠Back end demo

You can find a demo back-end image in the back-end-demo folder.

⁠Walk through

Update your /etc/hosts : echo "127.0.0.1 example.org" >> /etc/hosts

Start the front-end : docker run -d -p 80:80 iheve/serf-reverse-proxy

Access http://example.org/⁠ in your web browser. You will find the default nginx page. You stayed on the reverse-proxy container.

Start a demo-back-end : docker run -d -e "SERVICE_NAME=example.org" iheve/serf-reverse-proxy-be-demo

Access http://example.org/⁠ in your web browser. After less thant 30 secondes, you will find the default apache2 page. You went through the reverse-proxy container to hit the second container.

⁠Tips

If you need to connect through ssh, you might want to set the root password by adding to your Dockerfile : RUN echo "root:yourpwd"|chpasswd

Tag summary

Content type

Image

Digest

sha256:217f44583…

Size

86.2 MB

Last updated

almost 11 years ago

docker pull iheve/serf-reverse-proxy