wp-sqlite-db
wordpress-playground
Our great sponsors
wp-sqlite-db | wordpress-playground | |
---|---|---|
10 | 22 | |
532 | 1,523 | |
- | 1.4% | |
0.0 | 9.7 | |
2 months ago | about 13 hours ago | |
PHP | JavaScript | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wp-sqlite-db
-
WordPress Core to start using SQLite Database
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.
-
WordPress to support SQLite back end
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.
- WordPress testing official SQLite Support
-
WordPress WASM
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
-
A proposal to officially support SQLite in WordPress
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!
-
SQLite or PostgreSQL? It's Complicated
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...
- Wp-SQLite: WordPress running on an SQLite database
-
Lots of blocked attacks and probes..should I worry..
This wp-sqlite-db one. Not super active, but maintained, at least.
wordpress-playground
-
Things you forgot because of React
Sorry friend, WordPress already beat you to it: https://github.com/WordPress/wordpress-playground
- WordPress Playground: A WordPress that runs entirely in the browser
-
WordPress Playground: A WordPress that runs in the browser
> Is there a reason why using OPFS directly from SQLite doesn't work?
I'm guessing this means using SQLite WASM's built-in OPFS integration as described in these articles:
- sqlite3 WebAssembly documentation - Persistent Storage Options: OPFS - https://sqlite.org/wasm/doc/trunk/persistence.md#opfs
- SQLite Wasm in the browser backed by the Origin Private File System - https://developer.chrome.com/blog/sqlite-wasm-in-the-browser...
Within the Playground, SQLite interacts with the database file in MEMFS only, and the Playground coordinates the syncing from MEMFS to OPFS.
https://github.com/WordPress/wordpress-playground/tree/trunk...
The reason for this, I believe, is that the primary use case is/was to have the entire file system in memory, including SQLite's database file. This was the original implementation, and is still the default behavior. Persistence was later added as an optional feature.
The good news is that browser support for OPFS seems to be getting better. From the SQLite docs:
As of March 2023 the following browsers are known to have the necessary APIs:
-
WordPress Playground
One of the most exciting things at WordCamp Europe 2023 for me was discovering how far along the WordPress Playground project is. If you haven’t heard of the playground before, it’s a full version of WordPress, running directly in your browser!
-
WCGI: WebAssembly and CGI
WordPress has an official WebAssembly build for the browser and Node.js: https://developer.wordpress.org/playground https://github.com/WordPress/wordpress-playground
(Disclosure: I'm the creator)
-
WordPress testing official SQLite Support
I love the work going on there at WasmLabs, especially enjoying the articles with in-depth technical explorations.
After the article about running WordPress in the browser was published, there's a new project called WordPress Playground which is gradually preparing NPM or Composer packages to make it easier for people to run it.
https://github.com/WordPress/wordpress-playground/
They've been doing very detailed work, like making some patches to PHP and SQLite for improved compatibility with Emscripten, etc. It seems there's a lot of overlap with what WasmLabs has achieved and probably have continued to develop further. Perhaps there's an opportunity for collaboration.
- WordPress WASM
-
Hacker News top posts: Sep 25, 2022
WordPress WASM\ (28 comments)
What are some alternatives?
sql.js-httpvfs - Hosting read-only SQLite databases on static file hosters like Github Pages
marmot - A distributed SQLite replicator built on top of NATS
wp2static - WordPress static site generator for security, performance and cost benefits
dod - DOS on dope. The last MVC Web framework you'll ever need
WordPress - WordPress, Git-ified. This repository is just a mirror of the WordPress subversion repository. Please do not send pull requests. Submit pull requests to https://github.com/WordPress/wordpress-develop and patches to https://core.trac.wordpress.org/ instead.
webrcade - Feed-driven gaming
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.
wapm-cli - 📦 WebAssembly Package Manager (CLI)
trellis - WordPress LEMP stack with PHP 8.1, Composer, WP-CLI and more
Platform - Qbix Platform for powering Social Apps (http://qbix.com/platform)
jetpack - Security, performance, marketing, and design tools — Jetpack is made by WordPress experts to make WP sites safer and faster, and help you grow your traffic.
website - WebAssembly website