When to support mysql 8+?

Developer help
1

If you’re looking for some help, it’s important to provide as much context as possible so that people are able to assist you. Try to always mention:

  • What’s your URL? This is the easiest way for others to debug your issue
  • What version of Ghost are you using?
    latest
  • What configuration?
  • What browser?
  • What errors or information do you see in the console?
  • What steps could someone else take to reproduce the issue you’re having?
2

MySQL 8 is supported. If you can share specifics about the problems you are having maybe someone can help you :wink:

3

good job! but why not update “setup” Docs for mysql 8
by the way, “@blog” is also not updated to “@site”.

4

The setup docs always reference recommended versions. There has been little to no testing on mysql 8 outside of some developers using it locally in non-production scenarios (this is what I meant by “supported” - it’s not officially supported but I’m not aware of any known problems) which is why it’s not recommended. That’s why I asked what issues you were running into.

by the way, “@blog” is also not updated to “@site”.

This is theme dependent. Casper, the default theme, does not use @blog anywhere. If the theme you are using is showing that error then it’s worth opening an issue on the relevant repo if it’s open-source, or contacting the theme developer if it’s a commercial theme (note that some developers may choose to keep using @blog for the widest version support until the deprecation becomes an error).

5

I was unable to get ghost to work with mysql:8.0.24 with Kubernetes as an orchestrator.

Received: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client.

It seems to work fine with mysql:5.7.34.

Just an FYI in case others are reaching this page from Google :slight_smile:

6

This was fixed in ghost-cli@1.15.0, if you install the latest version you should be able to set up Ghost on MySQL 8.

1 Like
7

Thanks for sharing.
Have you updated the Docker registry as well?
I am running ghost:4.3.2, which is the latest version on Docker Hub, and this has the problem mentioned.

8

The docker image is an unofficial community-run effort, I’d suggest opening an issue there if you know there’s a problem.

9

Ah, all right - thank you for taking time to share insights on this, Kevin - appreciated.

As explained, I hope it can help others in the same situation as I was in.