[HN Gopher] WordPress testing official SQLite Support
___________________________________________________________________
WordPress testing official SQLite Support
Author : ethanpil
Score : 38 points
Date : 2022-12-16 21:36 UTC (1 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| c0nsumer wrote:
| This'd be great. I'm curious about performance, of course, but
| for personal blogs without comments, coupled with a caching
| module... This could be great.
|
| One thing I'm still trying to suss out is how to have Apache host
| Wordpress and stuff via HTTP/2. Wordpress which needs PHP which
| requires mpm_prefork, which precludes mod_http2. Guess I should
| just proxy WP to another instance of Apache or some other
| httpd...?
| jcoby wrote:
| Take a look at php-fpm. It works with all the major servers and
| let's them do what they do best and offloads the php requests
| to php when needed. It also has better caching and overall
| performance than mod_php since it's a long running daemon.
| adobrawy wrote:
| For people who are wondering if SQLite is the right database for
| Wordpress, I recommend taking a look at
| https://www.sqlite.org/whentouse.html where SQLite authors
| explains what sites it makes sense for.
|
| In short: for most of Wordpress deployment, especially for long
| tail of hair salons, car dealerships, personal blogs and other
| non-tech SME sites
| brian_herman wrote:
| Awesome.
| blacksmith_tb wrote:
| That's excellent, I have been sad to see Ghost lose support for
| SQLite[1]. I have been running a blog on it for years, works
| great.
|
| 1: https://github.com/TryGhost/Ghost/issues/14446
| danjoredd wrote:
| Is there any reason to want to use SQLite for Wordpress? Its
| always great to have more options, but Im unclear as to why
| someone would use that instead of MySQL
| upon_drumhead wrote:
| Complexity? I have a small site that would run just fine with
| SQLite. I'd switch over in a heartbeat.
| TrueSlacker0 wrote:
| Complexity? MySQL 1 click installs on damn near every
| WordPress install. I fail to see how it is complex.
| rchaud wrote:
| Someone's never seen a WP white screen of death because of
| some esoteric MySQL error the average person will have no
| idea how to debug.
| dharmab wrote:
| Keeping it updated and backed up is complex. Sqlite can be
| embedded inside an application (easy updates) and the
| database backup is a single file.
| LVB wrote:
| Zero clicks is better. And less resource usage, which can
| help on really small instances with multiple applications.
| pstuart wrote:
| I'm curious as to how much of your site _depends_ on
| WordPress, vs. just using a static site generator.
| Veen wrote:
| MySQL is a bit of a faff for the average person who wants to
| self-host WordPress. SQLite can be made more user friendly.
| Plus, MySQL is more expensive to host.
| jchulce wrote:
| SQLite would bring simpler installs, reduced administration
| needs, and a decreased attack surface.
| ergonaught wrote:
| Resource usage on a default MySQL install today is quite
| outrageous relative to what is needed for a typical blog.
| fpoling wrote:
| For a VM with a couple of wordpress blogs that I administer
| SQLight should allow to reduce memory from 4 to 2GB. In
| addition the blogs will no longer share the database improving
| security (while the blogs has the same Wordpress version the
| plug-in set is different, so a vulnerability in one is not
| necessary affects another).
| nix23 wrote:
| Because 99% of Wordpress installations would be much better of
| without any sql database, aka something like a git backend.
| pacifika wrote:
| Portable WordPress
| rchaud wrote:
| This is at least a decade overdue. I've moved my personal
| site to Pico CMS (flat-file) for precisely this reason.
___________________________________________________________________
(page generated 2022-12-16 23:00 UTC)