/PRNewswire/ -- K1 Investment Management, LLC ("K1"), one of the largest investors in small-cap enterprise software companies, today announced the completion...
Yeah the Open Source version. I doubt that the hosted version is using that. Cloud providers have super fast DB’s that are basically compatible with the MySQL syntax
There still is no documented way to migrate an existing WordPress to PostgreSQL. The PostgreSQL plugin assumes a fresh installation, everything else is not assumed to be there.
The AIO docker image put together by the NC team uses postgres. That’s the recommended way to install NC now, and having used a multitude of methods in the decade I’ve uses nextcloud, I 100% recommend the AIO image.
The virtualization shouldn’t have a negative effect, since containers are just using the host kernel so it’s not much extra overhead.
I would give it a try, it’s simple enough to set up docker on the pi, turn off your native NC install, and add the docker compose file and stand it up. Or build another SD card with a fresh raspbian install and swap it out.
Huh. I figured they changed to PG since that’s what their AIO image is using, and having used both myself in regular baremetal installs, postgres is by far the better performing backend.
My question was ironic, implying that anyone using it in a productive system/software/service is doing a very bad job at software architecture. I avoid any product relying on super slow software pieces.
Well, who is using mysql/mariadb nowadays anyways? If you haven’t made the switch to at least postgres in the past 5 years, you messed up anyways.
Wordpress
Yeah the Open Source version. I doubt that the hosted version is using that. Cloud providers have super fast DB’s that are basically compatible with the MySQL syntax
There still is no documented way to migrate an existing WordPress to PostgreSQL. The PostgreSQL plugin assumes a fresh installation, everything else is not assumed to be there.
Nextcloud.
Though I think it has some level of support for postgres by now. I should check on that.
I use NextCloud w/ Postgres and it works completely fine.
Great. It wasn’t too long ago that MariaDb was still the “recommended” option.
It’s still “recommended” and pretty much every tutorial I see uses it, but Postgres seems to work just fine.
I just checked the docs for installation instructions, it didn’t seem to make a distinction anymore.
It still is, as that’s what the developers use.
The AIO docker image put together by the NC team uses postgres. That’s the recommended way to install NC now, and having used a multitude of methods in the decade I’ve uses nextcloud, I 100% recommend the AIO image.
Is there a minimum system requirements? I have bare metal nextcloud on a raspi 4, 4 GB ram, and it’s pretty snappy.
I would consider migrating to the AIO version for more stability but IDK what toll the virtualization would take.
The virtualization shouldn’t have a negative effect, since containers are just using the host kernel so it’s not much extra overhead.
I would give it a try, it’s simple enough to set up docker on the pi, turn off your native NC install, and add the docker compose file and stand it up. Or build another SD card with a fresh raspbian install and swap it out.
nextCloud becomes notably faster when you migrate from MySQL to PostgreSQL.
It’s worked on Postgres for several years now, and it’s the preferred and recommended backend for NC.
As someone who self-hosted it, I can’t say this is true.
https://docs.nextcloud.com/server/latest/admin_manual/configuration_database/linux_database_configuration.html
Huh. I figured they changed to PG since that’s what their AIO image is using, and having used both myself in regular baremetal installs, postgres is by far the better performing backend.
The Go version?
Are you thinking of ownCloud Infinite Scale? NextCloud is still PHP.
Ah, yes. Thanks.
My question was ironic, implying that anyone using it in a productive system/software/service is doing a very bad job at software architecture. I avoid any product relying on super slow software pieces.
MySQL sucks, and almost everyone who willingly use it also sucks.