Skip the MySQL check

  • This answer suggests skipping the MySQL check.
  • From the ghost CLI tool, I can start with export GHOST_NODE_VERSION_CHECK=false to skip the Node version (because I’m using current Node.js).
  • Can I use something like that for MySQL?
    • What is the “skip MySQL check” version of export GHOST_NODE_VERSION_CHECK=false?

About MariaDB for open source

When MariaDB Server’s predecessor, MySQL, was bought by Oracle in 2009, MySQL founder Michael “Monty” Widenius forked the project due to concerns about Oracle’s stewardship, naming the new project MariaDB.

Most of the original developers joined the new project and MariaDB Server has continued to develop rapidly since then.

MariaDB is intended as a drop-in replacement for MySQL and MariaDB is FOSS too, probably more so. “Maintaining Ghost for multiple databases” isn’t necessary with MariaDB. In my experience, MySQL is the bigger troublemaker with compatibility and upgrades. If using MariaDB, upgrade tutorials might not even be necessary.

I like what Ghost is doing for the ex-WP community because PHP-FPM’s “fast CGI” just isn’t as fast as V8 under Node.js, but please tell me that I’m allowed discretion. I’ve never seen any app tell me that I must have MySQL and not MariaDB. As a SysAdmin it’s my job to handle these things, not JS experts. It’s a deal breaker.

Maybe I should apply to work for Ghost and help them iron this out.

In the meanwhile, can someone please help me skip this check that I just don’t need?

I’d suggest going through this thread first (specifically this reply). The tl;dr is that Ghost never supported MariaDB, but it “just worked” with MySQL 5. However, MySQL 5 is EoL, and MySQL 8 diverges from MariaDB enough that end-to-end compatibility cannot be guaranteed.

Coming to your question - I agree that it would be nice to tell the CLI to downgrade the error, but as a workaround, you might be able to get everything up-and-running with sqlite, and then update the config to use MySQL. You’ll have to manually create the user and database which isn’t ideal.

I like this response! As a SysAdmin, creating the database and user is actually easier for me.

So, are you telling me that this FAQ does not claim that SQLite3 will be depreciated?

I kinda like the SQLite concept, even tho I always used Monty’s SQL tools. If SQLite will not be depreciated, I can solve my basic problem by heading that way.

(Arguably, SQLite should be your roadmap preference over MySQL, if you were to choose between the two, especially with your feature of the ghost CLI tool handling so much that the SysAdmin usually does.)

I can’t speak for the Ghost team, but in the past they have stated that SQLite3 isn’t recommended for production, but it will be supported for development

1 Like

I finally got Ghost v5.94.1 on MariaDB, and Ghost is none the wiser, thinking it is MySQL. I have no problems what so ever.