Decoupled DB and Middleware for Self-Hosted using Docker Compose

In the self hosted documentation, it was recommended to decouple the DB with the rest of middleware but within the docker compose setup configured under the docker folder of the repo, they are all bundled into a single docker compose project.

I have created a very crude docker compose shell script and yaml file to decouple the DB component with the rest of the middleware... it comprise of 2 different docker compose project:

1. The DB service docker compose
2. The Middleware service docker compose

both are utilizing the same external docker network named after the environment variable PROJECT_NAME

I've created 4 shell script to initialize the service, stop, start and remove them.

This is a very crude way to do things for now just to achieve the objective of decoupling the DB and the Middleware components.

Someone could perhaps improve the approach that I have shown in my fork under 'decoupled' branch: [