blog: Legacy projects with unsupported PHP/MySQL versions using DDEV #375

garvinhicking · 2025-05-27T18:46:46Z

The Issue

I was encouraged through https://discord.com/channels/664580571770388500/1374723890500337724/1375138791278379084 to contribute my solution as a blog article.

How This PR Solves The Issue

I have documented my steps to the best of my knowledge.

Manual Testing Instructions

Run npm run build to see the article.

Automated Testing Overview

Only content, no changes of code.

Release/Deployment Notes

"Works on my machine". ;)

stasadev

Thank you!

Please check the linter errors https://github.com/ddev/ddev.com/actions/runs/15283249253/job/42987518863?pr=375

And my comments (I didn't make a full review yet.)

public/img/blog/2025/05/museums-victoria-Di7WfLcrJ_I-unsplash.jpg

src/content/blog/legacy-projects-with-unsupported-php-and-mysql-using-ddev.md

stasadev

I'll check it out in action tomorrow.

BTW, this is a good candidate for a DDEV add-on https://github.com/ddev/ddev-addon-template

src/content/blog/legacy-projects-with-unsupported-php-and-mysql-using-ddev.md

stasadev · 2025-05-28T13:35:22Z

src/content/blog/legacy-projects-with-unsupported-php-and-mysql-using-ddev.md

+Next I created the very small file `~/legacyphp/.ddev/docker-compose.db.yaml` in the same directory next to `config.yaml`:
+
+```yaml
+services:
+  db:
+    platform: linux/amd64
+    build:
+      args:
+        BASE_IMAGE: ddev/ddev-dbserver-mysql-5.5:v1.24.6
+```


This is an interesting workaround you discovered, but it's going to work only until the next ddev restart:

Failed to start legacyphp: unable to start project legacyphp because the configured database type does not match the current actual database. Please change your database type back to mysql:5.5 and start again, export, delete, and then change configuration and start. To get back to existing type use 'ddev config --database=mysql:5.5' and then you might want to try 'ddev debug migrate-database mysql:8.0', see docs at https://ddev.readthedocs.io/en/stable/users/extend/database-types/

I think we can probably inject platform:linux/amd64 for MySQL 5.5, 5.6 on arm64.

I opened this issue:

Inject platform: linux/amd64 for MySQL 5.5 and 5.6 on ARM64 ddev#7338

But I don't think we're going to implement this fast.

I propose to add a small note on this matter.

Oooh, shoot. That is unfortunate - I honestly only had to start it up once and left it open for some days, and never issued a restart. I wonder if this makes the whole point of the article moot now, if we do not have a way to re-execute the container.

So I'd possibly scrap the whole article now, if you don't see any other kind of workaround to bypass the database config.yaml assignment/validation. If we had an YAML option like "disable_validation" or so that would massively help of course...

You can try to:

copy-paste db service from .ddev/.ddev-docker-compose-base.yaml (replace uid value with ${DDEV_UID}, gid value with ${DDEV_GID}, but I don't know if it'll work in this context; if it doesn't work, leave it as it is with a note that people need to update these values.)

copy-paste .ddev/.dbimageBuild/Dockerfile to .ddev/mysql55/Dockerfile (or another folder) and update db>build>context with new folder location.

Use ddev config --omit-containers=db which adds omit_containers: [db] to .ddev/config.yaml

If the db service name doesn't work, use a different one.

(I haven't tried this. but I think there is a good chance it's going to work.)

Hm... I'm a bit afraid this "kills" the lightweightness the solution had before... I'm not so sure this would be a solution we should highlight as a blog entry then?

I would be okay to leave this blog entry dangling, if a ddev release allowing to influence the behaviour could be done at some point. Then we could add an info about the version requirement to the entry.. I am not in a hurry to publish this, but I also don't want to blow up the complexity too much.

Let’s put this PR in draft.

(No new releases this month or next while Randy is bikepacking.)

I found a workaround for this.

src/content/blog/legacy-projects-with-unsupported-php-and-mysql-using-ddev.md

Co-authored-by: Stanislav Zhuk <[email protected]>

garvinhicking · 2025-05-28T15:07:43Z

(thanks so much for the effort of going through the article and finding good improvements to it!)

stasadev

Please check the entrypoint I added.

If we decide to change some logic for MySQL 5.5 and ARM64 in the future, the blog can be modified.

src/content/blog/legacy-projects-with-unsupported-php-and-mysql-using-ddev.md

…l-using-ddev.md Co-authored-by: Stanislav Zhuk <[email protected]>

garvinhicking · 2025-05-30T06:09:17Z

Please check the entrypoint I added.

If we decide to change some logic for MySQL 5.5 and ARM64 in the future, the blog can be modified.

That looks like a clever and valid way to circumvent it, and is lightweight. That works for me! I've added a small note to explain this, what do you think? Thanks so much for going the extra mile on it :-)

stasadev

I've added a small note to explain this, what do you think?

I don't see it. Please add it and modify the pubDate (let's publish it on Monday or today).

Everything else looks ready.

stasadev

Thank you!

When you decide to write another blog, use a branch name other than main. It lets you work on multiple articles in parallel and makes review easier.

garvinhicking · 2025-05-30T10:44:23Z

Thank you!

When you decide to write another blog, use a branch name other than main. It lets you work on multiple articles in parallel and makes review easier.

Thanks a lot for the help. Yes, I noticed too I forgot to create a branch first. Will keep it in mind :-)

blog: Legacy projects with unsupported PHP/MySQL versions using DDEV

eb494d5

stasadev reviewed May 27, 2025

View reviewed changes

garvinhicking added 5 commits May 27, 2025 20:59

fix: capitalize terms

9b272d8

chore: apply suggestions from review

5598244

chore: npx prettier --write

83a1318

chore: use apache markdown code block language

bc6415f

fix: fix grammar

7406c8a

stasadev reviewed May 27, 2025

View reviewed changes

stasadev self-requested a review May 27, 2025 19:21

This was referenced May 28, 2025

Inject platform: linux/amd64 for MySQL 5.5 and 5.6 on ARM64 ddev/ddev#7338

Open

ddev ssh should be able to accept user and shell ddev/ddev#7339

Open

stasadev requested changes May 28, 2025

View reviewed changes

Apply suggestions from code review

9f852df

Co-authored-by: Stanislav Zhuk <[email protected]>

stasadev self-requested a review May 28, 2025 15:16

stasadev marked this pull request as draft May 28, 2025 15:27

stasadev reviewed May 28, 2025

View reviewed changes

src/content/blog/legacy-projects-with-unsupported-php-and-mysql-using-ddev.md Show resolved Hide resolved

src/content/blog/legacy-projects-with-unsupported-php-and-mysql-using-ddev.md Outdated Show resolved Hide resolved

garvinhicking and others added 2 commits May 30, 2025 08:06

Update src/content/blog/legacy-projects-with-unsupported-php-and-mysq…

8028a5b

…l-using-ddev.md Co-authored-by: Stanislav Zhuk <[email protected]>

Update src/content/blog/legacy-projects-with-unsupported-php-and-mysq…

a3f14c8

…l-using-ddev.md Co-authored-by: Stanislav Zhuk <[email protected]>

stasadev approved these changes May 30, 2025

View reviewed changes

stasadev marked this pull request as ready for review May 30, 2025 10:22

garvinhicking added 2 commits May 30, 2025 12:26

chore: add note

f6dc4c1

chore: adjust pubdate

dce721c

stasadev approved these changes May 30, 2025

View reviewed changes

stasadev merged commit 03ec949 into ddev:main May 30, 2025
1 check passed

Uh oh!

blog: Legacy projects with unsupported PHP/MySQL versions using DDEV #375

blog: Legacy projects with unsupported PHP/MySQL versions using DDEV #375

Uh oh!

Conversation

garvinhicking commented May 27, 2025

The Issue

How This PR Solves The Issue

Manual Testing Instructions

Automated Testing Overview

Related Issue Link(s)

Release/Deployment Notes

Uh oh!

stasadev left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

stasadev left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

stasadev May 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

garvinhicking May 28, 2025

Choose a reason for hiding this comment

Uh oh!

stasadev May 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

garvinhicking May 28, 2025

Choose a reason for hiding this comment

Uh oh!

stasadev May 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stasadev May 28, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

garvinhicking commented May 28, 2025

Uh oh!

stasadev left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

garvinhicking commented May 30, 2025

Uh oh!

stasadev left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stasadev left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

garvinhicking commented May 30, 2025

Uh oh!

Uh oh!

stasadev left a comment •

edited

Loading

stasadev May 28, 2025 •

edited

Loading

stasadev May 28, 2025 •

edited

Loading

stasadev May 28, 2025 •

edited

Loading

stasadev left a comment •

edited

Loading