It’s too late for me now coz I didnt do my research and ive already migrated over, but good god ever loving fuck was the AIO container the hardest of all my services to set up.
Firstly, it throws a fit if you don’t set up the filesystem specifically for php and the postgres db as if it were bare metal. Idk how or why every other container I use can deal with UID 568 but Nextcloud demands www-data and netdata users.
When that’s done, you realise it won’t run background tasks because it expects cron to be set up. You have to set a cronjob that enters the container to run the cron, all to avoid the “recommended” approach of using a second nextcloud instance just to run background tasks.
And finally, and maybe this is just a fault of TrueNAS’ setup wizard but, I still had to enter the container shell to set up a bunch of basic settings like phone region. come on.
It’s too late for me now coz I didnt do my research and ive already migrated over, but good god ever loving fuck was the AIO container the hardest of all my services to set up.
Firstly, it throws a fit if you don’t set up the filesystem specifically for php and the postgres db as if it were bare metal. Idk how or why every other container I use can deal with UID 568 but Nextcloud demands www-data and netdata users.
When that’s done, you realise it won’t run background tasks because it expects cron to be set up. You have to set a cronjob that enters the container to run the cron, all to avoid the “recommended” approach of using a second nextcloud instance just to run background tasks.
And finally, and maybe this is just a fault of TrueNAS’ setup wizard but, I still had to enter the container shell to set up a bunch of basic settings like phone region. come on.
Straight up worse than installing it bare metal