Simplified Setup Management

Goal

Operators should be able to easily manage the setup for a Cubbles Base instance. As sometimes different setups might be based on a shared set of resources, it should be possible to easily merge different sets of resources.

Changes

Improvements

BASE-15: OperationsManager are allowed to split customisations into several files and folders

Releated Releases

Base-1.2 should be managed with the Base Remote-Control >= v4.0.0

Simplified Setup and Operations

Goal

This release is a step forward to the goal, that we do not want operators to have much effort to run the Cubbles-Base their own host.

Changes

Improvements

1. Automated Restart: By default, the Base automatically restarts in case of a server reboot.

   Note: For developers running a local Base using docker-machine and virtual-box if you stop your virtual-box ($ docker-machine stop cubbles-base-local) the Base will be restarted automatically if you start the virtual-box again ($ docker-machine startcubbles-base-local).

2. Removed Environment Releated Resources: The Base container no longer contains any environment releated resources. Instead it expects a docker-compose-custom.yml to be mounted to a /opt/base/etc/custom folder.

Bugfixes

1. Backup: The new implementation creates backups into the /backup folder of the base.coredatastore container. By mounting an external location onto this folder, you can define where to store the backups within you environment. The mount is a custom-configuration, to be done via the docker-compose-custom.yml mentioned above.