Description
Is there an existing issue for this?
- I have searched the existing issues
Name of mod
nextcloud-notify-push
Name of base container
nextcloud
Current Behavior
When initializing, the mod checks the nextcloud/apps
folder for the notify_push
app, but nextcloud allows setting multiple locations for apps in config.php (apps_paths
). This is also mentioned in the linuxserver.io README for the nextcloud image, which implies changing this configuration value is supported.
Because of the hardcoded check within the apps
folder, the mod init will fail even if the required app is installed, but just in a different location specified within config.php
Expected Behavior
Ideally, the check would be fleshed out to parse config.php and check all paths listed under apps_paths
, but at the very least documentation should be added to the mod README stating that it does not work if the notify_push
app is not installed to nextcloud/apps
specifically.
Steps To Reproduce
- Add a second app path to config.php -> apps_paths and set the
writeable
flag of the default one that points toapps
tofalse
- Install the
notify_push
app from the nextcloud app store, notice it goes to the second folder that was just added - Install this mod via the env variable
- Restart the container and watch the mod fail to find the app
Environment
- OS: TrueNAS Scale 25.04
- How docker service was installed: Part of the distribution
CPU architecture
x86-64
Docker creation
N/A
Container logs
nextcloud-app | **** Making sure the Nextcloud Client Push plugin is installed and enabled ****
nextcloud-app | notify_push already installed
nextcloud-app | notify_push already enabled
nextcloud-app | **** Notify-push folder not found. I
Metadata
Metadata
Assignees
Labels
Type
Projects
Status