Skip to content

Conversation

@GROwen
Copy link
Contributor

@GROwen GROwen commented Jan 23, 2026

Motivation

Preparation for mysql 8 upgrade

Changes

Added mysql 5.7 compatible collation and avoids mix of collations.

@nicksantamaria
Copy link
Contributor

/build

@nicksantamaria
Copy link
Contributor

@GROwen do we want to wait for backend to test the pr-416 tag before merging?

@GROwen
Copy link
Contributor Author

GROwen commented Jan 23, 2026

@nicksantamaria I don't think it's necessary but we do need to bump the tag for mariadb. Lagoon's updated the naming convention to couple them specifically to MariaDB versions. I'll post a commit in a sec.

FROM uselagoon/mariadb-drupal:latest
FROM uselagoon/mariadb-10.11-drupal:latest

ENV MARIADB_CHARSET=latin1
Copy link
Contributor Author

@GROwen GROwen Jan 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've removed these values because they are set in the connection block in bay/settings.php, in the case of collation and in the case of the charset we should use the default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants