fix database service names in docker-compose-xx.yml

[ggruening]

Description

This pull request addresses issues in the docker-compose-mysql.yml and docker-compose-mariadb.yml files related to the naming of the database services. Currently, both the MySQL and MariaDB containers have inconsistent service names. The MySQL container is defined under the service name db, while the application container attempts to connect to it using the name mysql. Similarly, the MariaDB container is also misconfigured. These discrepancies can lead to connection issues, particularly when the stack is integrated into a more complex environment, such as when the container is behind a reverse proxy. Using the correct service names is also a cleaner and more maintainable approach, regardless of the environment in which the stack is deployed.

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've written tests (if applicable) for all new methods and classes that I created. (rake test)
• I've added documentation as necessary so users can easily use and understand this feature/fix.

After making these changes, I ran the Docker Compose setup and verified that the application can now connect to both the MySQL and MariaDB databases without any issues.

[github-actions]

Hello @ggruening, thank you for submitting a PR! We will respond as soon as possible.

[pglombardo]

Great find thanks @ggruening!