Reframe app design into a docker compose network - Path to a simple packaged distributable

[Kamal-Eldin]

Description

• The current app design is based on a single monolith where both the front and backend services are containerised into a single container.
• The database is expected to be set up on the host system by the user
• The user is expected to setup both the front and backend services

This layout offloads a considerable technical overhead on the user's end, especially the database setup which varies based on the user's host system. In this case the user cannot be assumed to be a typical data annotator or a collector, but rather a tech savy developer.

Goal

• to reach a simple path to setup and install the app for the convenience of non tech-savy users, whom are typically the expected profile for data annotation and collection.
• Unify all services within a single management system

This opens the door to package the project as a simple distributable with minimal user interaction

Desired Behavior

1. A simple command to launch or stop the whole system and dependencies, example via a Make target or a shell command.
2. A unified OS agnostic installation and configuration system
3. Provide a reliable solution to manage secrets for all services

Current Behavior

• The end user is expected to own the configuration and installation.
• The installation path is fragmented into 3 sections (i.e., frontend, backend, database)
• Secrets are expose as environment variables