nextcloud32: notify_push broken with sqlite

[d4g]

Nixpkgs version

• Unstable (26.05)

Describe the bug

Using sqlite on nextcloud, the string DB url is created in a wrong way:

export DATABASE_URL="sqlite://nextcloud@localhost/nextcloud"

Instead of

export DATABASE_URL=sqlite:///var/lib/nextcloud/data/nextcloud.db

For now i patched the service:

  serviceConfig = {
    # Replace the script-based ExecStart with a direct command
    ExecStart = lib.mkForce [
      ""
      "${pkgs.nextcloud-notify_push}/bin/notify_push /var/lib/nextcloud/config/config.php"
    ];

    # Set the environment variable BEFORE exec
    Environment = [
      "DATABASE_URL=sqlite:///var/lib/nextcloud/data/nextcloud.db"
    ];
    };
  };

I think that setting the DATABASE_URL via environment of the systemd service is also probably the better way.

Steps to reproduce

• Configure nextcloud with sqlite
• Enable notify_push
• Read the errors in the log, that the file cannot be found.

Expected behaviour

The URL is correctly created for sqlite

Screenshots

No response

Relevant log output

Additional context

No response

System metadata

• system: "x86_64-linux"
• host os: Linux 6.14.11-4-pve, NixOS, 26.05 (Yarara), 26.05pre919991.cad22e7d996a
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.31.2+1
• channels(root): "nixos"
• nixpkgs: /nix/store/ricxl8ir2gagb2ys4lhzgqrkcanvzsj7-nixos/nixos

As container on proxmox

Notify maintainers

@bachp @britter @dotlambda @Ma27 @provokateurin

---

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.

[SuperSandro2000]

I think that setting the DATABASE_URL via environment of the systemd service is also probably the better way.

We cannot load the DATABASE_PASSWORD env via Environment, so we cannot fully get rid of the script.

Configure nextcloud with sqlite

This is only recommended by upstream for local development, so you should probably switch to either postgres or mariadb.

[SuperSandro2000]

DATABASE_URL=sqlite:///var/lib/nextcloud/data/nextcloud.db

According to https://search.nixos.org/options?channel=unstable&show=services.nextcloud.datadir&query=Nextcloud*data the database should not be there. I use nextcloud with a postgres, so I cannot test this. Please open a PR which fixes the condition and uses the proper nextcloud variables to get the sqlite directory.

[Ma27]

I'd expect it to be reproducible though with the sqlite test, no?

This is only recommended by upstream for local development, so you should probably switch to either postgres or mariadb.

I mean, given "you shouldn't use that" and you not being able to reasonably test this, it'd be fair IMHO to just don't support the sqlite case with notify_push.

[SuperSandro2000]

I don't think we have a test case for notify_push at all.

[Ma27]

It's small, but https://github.com/NixOS/nixpkgs/blob/master/nixos/tests/nextcloud/with-postgresql-and-redis.nix#L66-L68 ?

[provokateurin]

I'm strongly against adding any kind of support for sqlite. It should never be used, not even on a very small single user instance. It's only for development purposes and we should maybe consider adding assertions that prevent using sqlite at all.

[Ma27]

The thing is, there's support, however it's broken.
I'm fine with dropping support for sqlite on that end, but we have to make that explicit.