wp-sqlite-db VS jetpack

Before they added SQLite as WP plugin, I would use https://github.com/aaemnnosttv/wp-sqlite-db/ and I would use `define('DB_DIR', '/absolute/custom/path/to/directory/for/sqlite/database/file/');` to define the database location of my choice; I believe they would let users do the same with core support.

They basically took this implementation and just adapted it to coding standards:

https://github.com/aaemnnosttv/wp-sqlite-db

This has been around since some time and is itself a fork of a previous work.

The interesting part is that this drop-in replacement (mostly) already works well, there are a few issues that are related to some quirks in the WordPress core itself, for example: https://github.com/aaemnnosttv/wp-sqlite-db/issues/18

And maybe now they will be fixed.

Author here, here's an in-depth writeup on how this works and why it's useful:

https://make.wordpress.org/core/2022/09/23/client-side-webas...

To answer your questions directly:

WebAssembly is the magic sauce that transforms server-side code into client-side code. MySQL unfortunately is not yet supported by WebAssembly, so I applied a plugin that adds SQLite supports to WordPress [0]. The WebAssembly application has its own in-memory filesystem that lives in a specific browser tab and is scraped as soon as you close it.

So – technically it exposes db credentials, and even the entire DB, but that you are the only user of that DB so it's okay.

> What would the backend look like

The only backend is a static file server where the code and the database live. Your browser downloads a copy of the database and allows you to modify it in the current tab, but the updates are never saved back to the server.

[0] https://github.com/aaemnnosttv/wp-sqlite-db

1. Plugins that register their own database tables (however there already exists prior art such as https://github.com/aaemnnosttv/wp-sqlite-db for handling these cases)

2. Plugins that do direct queries against the standard database schema (broadly either for invalid (bad code) or performance (valid but slim use case) reasons)

Also, WordPress would of course keep the old query functions around and they would likely add a tag to the plugin repository so authors can mark plugins as supporting thes new ORM features.

Great idea in my opinion!

There's a WordPress plugin that adds support for SQLite as an alternative to MySQL.

Apparently it works really well. The implementation is (to my) simply astonishing: they run regular expressions against the SQL to convert it from MySQL dialect to SQLite! https://github.com/aaemnnosttv/wp-sqlite-db/blob/9a5604cce13...

This wp-sqlite-db one. Not super active, but maintained, at least.

JetPack

Uptime refers to the amount of time your website is available and accessible to users. Monitoring uptime is crucial as frequent downtime can negatively impact your SEO rankings and user experience. Tools like Uptime Robot, Pingdom, and Jetpack’s downtime monitoring can notify you the moment your site goes down, allowing you to take immediate action.

The former is possible, as mentioned here, but the latter isn't. Emails include no trackers. It is however possible that at some point in the future, email openings for Jetpack Subscription emails will be available as part of Jetpack Stats. This suggestion is currently tracked here.

If they are using Jetpack, they could be appearing in the WordPress Reader on the app.

I didn't spend time looking for specific features, as much as pointing out the standard is to be extremely hand wrangled and therefore prone to such issues. I have no idea if this sort of nonsense (this is an official Automattic plugin) is going to work in SQLite:

https://github.com/Automattic/jetpack/blob/2447e267e40f2d133...

But certainly creating a new table with ENGINE= which you can also find in that file isn't likely to work as intended on other platforms.

We must understand Jetpack for WordPress as an extension of WordPress functionalities that technically and theoretically should be included in the native WordPress base installation, but because that would overload the WordPress “core” a lot, they are distributed in a mega-plugin: Jetpack for WordPress.

Can anyone help with this? It's hard to believe that setting up shipping is this cumbersome. I'm assuming WordPress.COM wants you to install something else. I use WordPress.ORG. Yes, I've also set up JetPack.com. IDK what other rabbit hole Automattic tricks you into going down, but I've gotten this far and quite frankly, the front end should be much easier than installing Linux+AWS Infrastructure. Anyways can anyone help?

so THAT’S why my site using jetpack.com‘s site accelerator completely fucking melted

Not to mention that hovering over the link would've shown it was jetpack.com.