Hello 
I am a newbie to the use and implementation of Nextcloud-AIO. Very very nice ! Daily backups and automatic updates (since 5d) are running smooth,
until the update of notify_push v0.6.3 to v0.6.4.
The topic “AIO Notify Push container does not start (Permission denied)” is marked as solved,
nevertheless the issue is not solved by the Nextcloud-AIO solution itself, is it ? Will it be automatically solved with the next daily update(s)?
I’m asking to find out if the automatic update process is a good choice.
According to the update policy
software components are under “test rounds” before pushed to AIO.
A computer scientist can solve it, but will it be solved without - by the Nextcloud-AIO itself ?
Best Greetings, Ive
Using: All-in-One VM image
https://download.nextcloud.com/aio-vm/
Nextcloud AIO v7.5.1
Nextcloud Hub 6 (27.1.3)
Using the integrated
Daily backup and automatic updates
Update
notify_push v0.6.3 to v0.6.4
03:00 UTC at Nov 9 23
database_dump.sql
before:
notify_push installed_version 0.6.3
notify_push types filesystem
after:
notify_push installed_version 0.6.4
notify_push types filesystem