Introduction
I’d like to propose the addition of a method by which an instance of the CMS container can be run with or without scheduled tasks.
User Story
A Xibo administrator who wants to run Xibo in a high-availability environment, such as Docker Swarm or Kubernetes, is forced to run the entire CMS in one container. This creates a race condition between multiple instances of the CMS when executing scheduled tasks. The race condition intensifies as more CMS instances are added to the cluster.
Suggested implementation options are an added environment variable that enables or disables tasks in a given instance of the container, or separation of all background processes into their own worker container.
For the dev team to fill in:
Status
The current status and the username of the:
- Reporter
- Drafter
- Implementer
Implementation
A broad description of the changes required.
Effected Software
Which parts of Xibo are effected
DB Schema Changes
Any necessary DB Schema Changes