Skip to content

Microservices with Docker, Flask, and React from testdriven.io

Notifications You must be signed in to change notification settings

Bi0max/testdriven-tutorial

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Tutorial on Microservices with Docker, Flask, and React

Build Status

ToDo:

  1. Fix TravisCI pipeline, which isn't working as expected because:
    1. Docker-compose exec always return exit code 0, not an error code of the command
    2. Sometimes tests start before PostgreSQL server is started

Docker Toolbox for Windows configuration

  1. Confiure VirtualBox to have access to the volume folder
    1. Set env variable TESTDRIVEN_ROOT_FOLDER (only for Windows), it will be used in docker-compose-dev.yml. For more info, check this.
    2. Refer to it from docker-compose "volumes" or from docker run "-v" option
    3. Refer just by the name you gave it in the settings (Shared Folders) of VirtualBox
  2. SSH into docker machine as root
  3. Other possibly useful Docker commands
  4. Use git-bash with "winpty" to run interactive docker session: winpty docker exec -it

PyCharm

  1. Add additional paths to interpreter, so that it sees the "project" folder of different services.

Comments to certain parts

Part 2, Chapter 8

  1. Exclude second volume ('/usr/src/app/node_modules') from docker-compose-dev.yml to make things work.
    It is a workaround. Normally it should work. But npm install is not installing fork-ts-checker-webpack-plugin in the Docker container.

Other

  1. docker exec in git-bash on Windows
  2. Use CMD tail -f /dev/null in the Dockerfile to be able to run the container indefinitely.

About

Microservices with Docker, Flask, and React from testdriven.io

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published