Date

Attendees

Goals

  • Encapsulate micro-services as services within a docker-compose network
  • Utilize Nginx as the entry point to all of the services

Discussion items

ItemWhoNotes
Encapsulate micro-services

Ralph A. Navarro Jr.

Host Requirement

The tests should work against these test environments

Utilize Nginx

Ralph A. Navarro Jr.

Website to Schedule
Sequence Table

Website to Schedule
Sequence Diagram

Action items


2 Comments

  1. Candy O'Sullivan (Sutherland)

    Homework:

    Which is the best way to link "website, frontend, backend, Mongo, Mongoexpress" micro-services to Internet (Port 80:80)?

    1. server /etc/hosts file (SharedIP micro-service names...) 
    2. docker .yml files - change "/" location to "/microservicename" creating sub-directories and links under /sites-available/ 

  2. Ralph A. Navarro Jr.

    What we did was to utilize Nginx as the entry point to all of the services.  We did this with nginx config files.  Nginx listens on port 80 and based on the hostname (i.e. website.sdb, backend.sdb, frontend.sdb, mongo.sdb), nginx redirects the packets to the appropriate port that the requested service is listening on.

    For local environments, we set the /etc/hosts file with your IP address that the services are running on.  For docker toolbox, that hosts file config line would like so:

    • 192.168.99.100    sdb nginx.sdb frontend.sdb backend.sdb mongo.sdb mongo-express.sdb