Change:
Steps to reproduce the behavior: a minimal config file with Nextcloud In console In (most revelent part) In we can find <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
is this a fresh install or did you try to modify an existing install?
From a fresh install
I didn't expect that, but reproducible for me with mysql and wouldn't be surprised if postgresql has the same issue. Incidentally, this is done by default for the sqlite test and it works fine there. Will take a look ~tomorrowish, need some sleep now.
See , this doesn't seem supported anymore, I just forgot tot ake care of the deprecation, sorry! deprecates this, from now on you'll get a warning when trying to do this.
Thanks for the quick correction. I have one last question. I want to migrate an existing Nextcloud instance that has this prefix. So if this option disappears from the NixOs options, what do I do?
So the module warning points out that you should add the option manually in . Possibly it could also work that you define it via and this will land indirectly in the over the generated
My observation is that the should already be in because nextcloud explicitly writes that into this file on install. Please check if that's the case and if so, you can just remove the option from your system config as explained in the warning. The suggestion to add it on your own is mostly there because I'm not sure if that's the case in all installations and I wanted to make sure people don't break their setup over this.
I have a different prefix than the default ("nc" VS "oc"), so I'll test with At worst, I'll export/import data of each app through their interface, hoping it's possible and goes well.

Discussion:
dbtableprefix = mkOption { type = types.nullOr types.str; default = null; <del> description = "Table prefix in Nextcloud's database."; </del> <ins> description = '' Table prefix in Nextcloud's database. __Note:__ since Nextcloud 20 it's not an option anymore to create a database schema with a custom table prefix. This option only exists for backwards compatibility with installations that were originally provisioned with Nextcloud <20. ''; </ins> }; adminuser = mkOption { type = types.str;

Using config.services.nextcloud.poolConfig is deprecated and will become unsupported in a future release. Please migrate your configuration to config.services.nextcloud.poolSettings. '') <ins> ++ (optional (cfg.config.dbtableprefix != null) '' Using `services.nextcloud.config.dbtableprefix` is deprecated. Fresh installations with this option set are not allowed anymore since v20. If you have an existing installation with a custom table prefix, make sure it is set correctly in `config.php` and remove the option from your NixOS config. '') </ins> ++ (optional (versionOlder cfg.package.version "25") (upgradeWarning 24 "22.11")) ++ (optional (versionOlder cfg.package.version "26") (upgradeWarning 25 "23.05")) ++ (optional (versionOlder cfg.package.version "27") (upgradeWarning 26 "23.11"))

services.nextcloud = { enable = true; datadir = "/var/lib/nextcloud-data"; <del> config.dbtableprefix = "nixos_"; </del> autoUpdateApps = { enable = true; startAt = "20:00";