Maximilian Bosch e1e15974f8 nextcloud20: drop ... The version 20 of Nextcloud will be EOLed by the end of this month[1]. Since the recommended default (that didn't raise an eval-warning) on 21.05 was Nextcloud 21, this shouldn't affect too many people. In order to ensure that nobody does a (not working) upgrade across several major-versions of Nextcloud, I replaced the derivation of `nextcloud20` with a `throw` that provides instructions how to proceed. The only case that I consider "risky" is a setup upgraded from 21.05 (or older) with a `system.stateVersion` <21.11 and with `services.nextcloud.package` not explicitly declared in its config. To avoid that, I also left the `else-if` for `stateVersion < 21.03` which now sets `services.nextcloud.package` to `pkgs.nextcloud20` and thus leads to an eval-error. This condition can be removed as soon as 21.05 is EOL because then it's safe to assume that only 21.11. is used as stable release where no Nextcloud <=20 exists that can lead to such an issue. It can't be removed earlier because then every `system.stateVersion < 21.11` would lead to `nextcloud21` which is a problem if `nextcloud19` is still used. [1] https://docs.nextcloud.com/server/20/admin_manual/release_schedule.html		2021-10-25 01:34:47 +02:00
..
basic.nix	nixos/nextcloud: fixup #119638	2021-10-09 22:45:31 +02:00
default.nix	nextcloud20: drop	2021-10-25 01:34:47 +02:00
with-mysql-and-memcached.nix	nixos/nextcloud: drop adminpass/dbpass options entirely	2021-10-08 18:30:57 +02:00
with-postgresql-and-redis.nix	nixos/nextcloud: run tests against each Nextcloud instance	2021-10-01 17:03:32 +02:00