The requirements asked for a web UI. You are right though, except for that, other kind of shared folder solutions might work.

Wordpress has become an all-purpose CMS known security vulnerabilities via unsafe plugins.

Ghost has APIs instead of plugins for nearly everything, so it eliminated a lot of security and maintenance headache that way.

Ghost focuses on just a few features centered around independent content creators: blogging, email newsletters and subscriptions.

So features for sending bulk emails and accepting payments are built in, but you won’t find native support for other things like podcasts or recipe markup.

Ghost meets my need, and I love not dealing with 30 plugins at risk of being exploited if I don’t upgrade them promptly.

Exactly. It’s not just downtime to worry about, either. It’s disks filling up. It’s hardware failure. It’s DNS outages. It’s random DDoS attacks. It’s automated scans of the internet targeting WordPress. It’s OS, php and database upgrades. It’s setting up graphing, monitoring, alerting and being on-call 24/7 to deal with the issues that come up.

If these businesses are at all serious, pay for professional hosting and spend your time running the business.

Until it gets a security audit, I’ll stick with Signal.

I use KDE Connect for laptop to desktop transfers.

Tried it a couple times. Went back to the CLI.

If you know the CLI or are willing to learn, the GUI is yet-another layer for bugs to exist.

I think there is a catch-22.

pg_dump needs to connect to a running PostgreSQL instance.

But if you upgrade the binaries and try to start up, you can’t because the old data format doesn’t work. Because you can’t start up, pg_dump can’t connect.

I’ve spend more than a decade supporting both Postgres and MongoDB in production.

While they each have quirks, I prefer the quirks of Postgres.

I just spent a massive amount of time retooling code to deal with a MongoDB upgrade. The code upgrade is so complex because that’s where the schema is defined. No wonder MongoDB upgrades are easier— the database has externalized a lot of complexity that now becomes some coders problem to deal with.

For minor version upgrades, the database remains binary compatible. Nothing to do.

The dump/restore required during major upgrades allows format changes which enable new features and performance improvements without dragging around cruft forever to stay backwards compatible.

For professionals running PostgreSQL clusters in production there is a way to cycle in the new server version with zero user-visible downtime.

Discussions about hosting on your hardware is more likely to be discussed as “homelab”.

It doesn’t improve security much to host your reverse proxy outside your network, but it does hide your home IP if you care.

If your app can exploited over the web and through a proxy it doesn’t matter if that proxy is on the same machine or over the network.

I would recommend automating only daily security updates, not all updates.

Ubuntu and Debian have “unattended-upgrades” for this. RPM-based distros have an equivalent.

What do you check two hours later?