Docker based production environment

Web applications use many development tools. So simple interpreting technologies become have few building stages. So on the production environment we need only builds. It is not the best practice keeping builds on a code revision system.

All changes are usually moved through repository. Here we are moving all changes by containers keeping build sources in containers. Containers are stored at, fetched from Docker Hub. It provides the robust modularity system making replicating and updating processes structural. This is a common Web application with real time functionality based on socket.io technology. Nginx is used for proxy requests to separate procession of logic and static files reducing the load of the node container. Server and client sources are also separated into dedicated containers to make exchange process easier. These are most unstable containers these are changing frequently. Containers are divided into levels: a level of infrastructure and a level of application logic. Containers of the application level are updating frequently. Some containers could be a volumes because they are used as volumes. But they are containers because they a populated by Docker Hub and they are fetched by docker-compose. The container based approach is more like to a product way that we provide to our clients. To receive such image run the docker compose file from here.