db-docker shortcomings and improvements

[hussainweb]

Based on the usage and experience so far, I am trying to determine a course of future and new updates for db-docker. Some of the shortcomings and reasons for why db-docker could be replaced are outlined here:

• db-docker can’t deal with assets - images that are referred to from the database. The solution was to use stage file proxy which puts it out of the ecosystem.
• db-docker is complicated to use.
  • Handling databases across branches gets tricky.
  • Trying to maintain a sacrosanct copy of database is a losing battle. People would give up using this rather than keep a lite version of database.
  • It is difficult to keep configuration updated to use the relevant version of MariaDB or underlying image.
  • It’s tricky to stay in step with updates by tools like Lando and DDEV. DDEV releases new versions of database frequently. This means that the team should use the same version of DDEV all the time or risk using an incompatible version of the database image.
  • It’s difficult to obtain a copy of the database from the Docker image directly. For example right now, on some projects, the Lando environment is quite behind and there is no way to get the database copy directly so that I can put it in DDEV.