# Skip the MySQL check

**URL:** <https://forum.ghost.org/t/skip-the-mysql-check/50452>\
**Category:** Self-hosting\
**Created:** [September 21, 2024, 4:33pm UTC](https://forum.ghost.org/t/skip-the-mysql-check/50452 "2024-09-21T16:33:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JesseSteele](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jessesteele/32/32175_2.png) [@JesseSteele](https://forum.ghost.org/u/JesseSteele)\
**Post date:** [September 21, 2024, 4:33pm UTC](https://forum.ghost.org/t/skip-the-mysql-check/50452/1 "2024-09-21T16:33:02Z")

</div>

- [This answer](https://forum.ghost.org/t/mariadb-nginx-failed-to-be-detected/27479/3) 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](https://mariadb.org/en/)…

> 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](https://mariadb.com/kb/en/mariadb-vs-mysql-compatibility/) and MariaDB is FOSS too, probably more so. “[Maintaining Ghost for multiple databases](https://forum.ghost.org/t/ghost-5-mariadb/32367/7)” isn’t necessary with MariaDB. In my experience, MySQL is the bigger troublemaker with compatibility and upgrades. If using MariaDB, [upgrade tutorials](https://forum.ghost.org/t/how-to-migrate-from-mariadb-10-to-mysql-8/29575) 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?

---

<div class="post-metadata">

**Author:** ![vikaspotluri123](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/vikaspotluri123/32/24_2.png) [@vikaspotluri123](https://forum.ghost.org/u/vikaspotluri123)\
**Post date:** [September 21, 2024, 5:39pm UTC](https://forum.ghost.org/t/skip-the-mysql-check/50452/2 "2024-09-21T17:39:45Z")

</div>

I’d suggest going through this thread first (specifically [this reply](https://forum.ghost.org/t/ghost-5-mysql-8-what-specific-functionality/30351/7)). 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.

> [@Ghost 5 + MySQL 8, what specific functionality?](https://forum.ghost.org/t/ghost-5-mysql-8-what-specific-functionality/30351):
>
> Hello! I’ve just heard about Ghost 5 only supporting MySQL 8, for this decision to be made, I reckon some research was done which led to the conclusion that justifies the choice, right? Can there be some more explanation on what specific findings of functionality that MySQL 8 offers, that isn’t available/compatible with MariaDB? Reason I’m asking is, that we currently run about 7 Ghost websites, all connected to MariaDB 10.4 and are planning to upgrade to MariaDB 10.7. But since we heard abo…

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.

---

<div class="post-metadata">

**Author:** ![JesseSteele](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jessesteele/32/32175_2.png) [@JesseSteele](https://forum.ghost.org/u/JesseSteele)\
**Post date:** [September 21, 2024, 6:23pm UTC](https://forum.ghost.org/t/skip-the-mysql-check/50452/3 "2024-09-21T18:23:24Z")

</div>

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](https://ghost.org/docs/faq/supported-databases/) 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.)

---

<div class="post-metadata">

**Author:** ![vikaspotluri123](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/vikaspotluri123/32/24_2.png) [@vikaspotluri123](https://forum.ghost.org/u/vikaspotluri123)\
**Post date:** [September 21, 2024, 7:50pm UTC](https://forum.ghost.org/t/skip-the-mysql-check/50452/4 "2024-09-21T19:50:18Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![JesseSteele](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jessesteele/32/32175_2.png) [@JesseSteele](https://forum.ghost.org/u/JesseSteele)\
**Post date:** [September 22, 2024, 10:50pm UTC](https://forum.ghost.org/t/skip-the-mysql-check/50452/5 "2024-09-22T22:50:08Z")

</div>

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.
