These images are used for production as well as development usage. Base-images are introduced where serveral images requires the same functionallity.
The following diagram depicts how the images are related during build.
Phusion Baseimage that acts as the ultimate base for all of our images. The image is based on ubuntu 18.04. See https://github.com/phusion/baseimage-docker for details.
Base image based on phusion. This image makes out the "os" part of our images, ie. this is where an update to OS-level things should land.
Any downstream image based on this image should focus on their particular need and finish off by clearing the apt-cache.
Basic php-functionality, note that we only install php-cli at this point.
Base-image for all nginx images.
Basic nodejs-functionality.
The static parts of the admin-backend, also acts as frontend for the php-fpm container.
PHP-FPM image ready for hosting the dynamic part of the admin backend.
Contains a source-release of the OS2Display administration, this is what you normally build prior to doing a prod-release.
NodeJS app that warps elasticsearch.
Elasticsearch server.
Nodejs app that wraps redis and handles websocket connections between screen and admin
Redis server.
The following diagram depicts the kubernetes objects used to host a single
OS2display environment.
