Add Docker Compose Deployment with MariaDB

[Carybe]

Summary:

This PR adds a Docker Compose configuration to set up a MariaDB instance, replicating the Toolforge infrastructure for local development.

Changes:

• Introduced docker-compose.yml for easy deployment.
• Configured MariaDB service to match production settings.

ToDo:

• Make sure that tests are working perfectly
• Add sql commands to MariaDB entrypoint so that test databases can be automatically created
• Documentation of deployment (probably replacing Makefile)
• Update CI accordingly

[lullis]

here you are defining a volume named "src", which is not needed because this is not at all related to the "./src" volume defined for the application service.

[Carybe]

you are right, I will remove it

[lullis]

The idea of 12factor is to have your application code constant and only change things based on environment variables. Here you are introducing conditional logic just for the sake of customizing the set up.

It is better to simply add different environment variables (and use sensible defaults) here and keep your application code the same:

DATABASES = {
"DATABASE_ENGINE": os.getenv("QSTS_DATABASE_ENGINE", "django.db.backends.mysql"),
"DATABASE_HOST": os.getenv("QSTS_DATABASE_HOST", "mariadb"),
"DATABASE_PORT": os.getenv("QSTS_DATABASE_PORT", 3306),
"DATABASE_USER": os.getenv("QSTS_DATABASE_USER", "qsts"),
"DATABASE_PASSWORD": os.getenv("QSTS_DATABASE_PASSWORD"),
}

[arcstur]

• Use root user in the docker-compose (it's dev, no need to complicate with extra users without permissions)
• Fix the tests by putting DB_ENGINE to sqlite or setup a MariaDB server
• Stop deploy from running, to perform the migration from SQLite to MariaDB