Difference between revisions of "KoBo Toolbox Requirements and Pre-requisites"

Step by step how-to instructions on installing and running KoBo Toolbox on a standalone server.
Jump to: navigation, search
m (Containers)
(Tag: visualeditor)
m (Containers)
(Tag: visualeditor)
Line 22: Line 22:
  
 
==== Containers ====
 
==== Containers ====
The actual work occurs within Containers. A container is a light-weight virtual machine - it uses the host machine’s Linux kernel, and consists of any extra files you add when the image is created, along with metadata associated with the container at creation or when the container is started. Each container is built from an image. The image defines the container’s contents, which process to run when the container is launched, and a variety of other configuration details.
+
The actual work occurs within Containers.  
 +
 
 +
A container is a light-weight virtual machine - it uses the host machine’s Linux kernel, and consists of any extra files you add when the image is created, along with metadata associated with the container at creation or when the container is started. Each container is built from an image. The image defines the container’s contents, which process to run when the container is launched, and a variety of other configuration details.
 +
 
 +
==== Registry ====
 +
Docker registry stores Images. After your Software vendor builds a Docker image and publishes (''pushes'') it to a public or a private Registry. it becomes readily-available to use in your system. From an usual software patching stand-point, it is pure magic: the application and its environment come pre-packed and ready to run. Patchied software (i.e. "with security updates installed") tends to have more environment-related issues, as the environment (i.e. the computer it is running on) changes with time, becoming less controlled or even unknown.

Revision as of 12:01, 21 December 2016

Docker owner
Top-level view of a Docker system from the (technical) owner's perspective

Running your own instance of KoBo Toolbox will put you in the role of the Owner, depicted in the diagram. The obvious pre-reqisite is a host, i.e. a hosting server with full administrative access.

KoBo Toolbox Setup procedure advises the installation of Docker Compose on 64bit Linux.This guide covers the operation on Ubuntu Linux Xenial. Other Ubuntu options require nearly the same procedure, while other Linux and othe OS installations may differ significantly, refer to Install Docker Compose.

Hosting server

  • Virtualized or preferably bare server:
    • Full CPU or more (2 cpu cores)
    • 4 GB RAM or more (2 gb ram)
    • 200 GB storage space (50 gb storage)
    • 50 GB backup storage (5 gb backup)
    • Internet connectivity
  • Ubuntu Xenial , v16.04.1 LTS

Docker engine

Practically the only software package that has to be installed on the Host, apart from OS packages and Git, is the Docker engine. That in effect means that most of the configuration, operation and maintenance tasks are performed through Docker;Familiarize yourself further with official Understanding Docker article and conneccted items.

Images

A Docker image is a read-only template with instructions for creating a Docker container. An image might contain an Ubuntu operating system with Apache web server and a simple web application installed. 

Images, or rather instructions how to obtain them on-line, are provided by the Software vendor. Except during the system setup stage, they are of little particular interest to the Owner in our context and will not explained in detail.Please refer to article on Docker.com for more information.

Containers

The actual work occurs within Containers.

A container is a light-weight virtual machine - it uses the host machine’s Linux kernel, and consists of any extra files you add when the image is created, along with metadata associated with the container at creation or when the container is started. Each container is built from an image. The image defines the container’s contents, which process to run when the container is launched, and a variety of other configuration details.

Registry

Docker registry stores Images. After your Software vendor builds a Docker image and publishes (pushes) it to a public or a private Registry. it becomes readily-available to use in your system. From an usual software patching stand-point, it is pure magic: the application and its environment come pre-packed and ready to run. Patchied software (i.e. "with security updates installed") tends to have more environment-related issues, as the environment (i.e. the computer it is running on) changes with time, becoming less controlled or even unknown.