Yes.
Funny…
Yes. I find that quite convenient because I can use the official NginX template by the Nextclouders.
I run a central reverse proxy based on Caddy on my OPNsense for SSL termination for all my publicly accessible jails.
Honestly I don’t know. I do. I use something like:
iocage list -h | awk '{ printf "iocage upgrade -r <RELEASE> %s\n", $2 }' | sh
for a major release upgrade and these commands for minor updates:
iocage list -h | awk '{ printf "iocage update %s\n", $2 }' | sh
iocage list -h | awk '{ printf "iocage exec %s pkg update\n", $2 }' | sh
iocage list -h | awk '{ printf "iocage exec %s pkg upgrade -y\n", $2 }' | sh
iocage list -h | awk '{ printf "iocage exec %s pkg autoremove -y\n", $2 }' | sh
iocage list -h | awk '{ printf "iocage restart %s\n", $2 }' | sh
followed by the standard occ upgrade procedure in for the Nextcloud jail.
HTH,
Patrick
1 Like
I guess I’m just more versed in caddy. Nginx has always seemed overly complicated with syntax and spacing, so I never bothered to learn it much.
@pmh How do you handle mount points?
Is the pkg version as simple as installing from pkg, enabling the services and voila?
I’m assuming things like redis, databases and such still have to be created and configured.
I have one mountpoint that is on my TrueNAS /mnt/hdd/data/nextcloud and inside the jail /var/nextcloud and that is that. That’s where all the files go.
You need to take the NginX template from Nextclouders, adapt it to the FreeBSD directories etc.
Then use the MySQL/MariaDB CLI to create a database and a user with matching credentials.
But that’s about “it”. Redis is just “enable, point Nextcloud at it”. No big deal.
But then I am a systems administrator for almost 30 years 
Sound about the same with the exception of caddy.
Very elegant!
Weekend = fiddling time. Just updated the Nextcloud jail to 13.4-RELEASE-p1. Flawless…
I will move to NC30 over the weekend. Now something i noticed when i update NC and this always happens: the update times out on the backup step. i don’t know why that happens but when use the back button in the browser and try again a couple of minutes later the updater allows me to proceed. Not sure why that is though.
1 Like
You are not supposed to use the web updater for any seriously large installation but the occ commandline tool or for a major version the updater.phar. It’s in the Nextcloud docs.
I wouldn’t call my installation “seriously large”. I don’t run any apps on it and have about 5 users of which only 2 very active, my accountant and me.
But me being lazy and you being all-knowing on NC in a TrueNAS Core environment, how would i go about if i would want to use updater.phar? Would it still be sudo -u www-data php updater/updater.phar?
Well, i am not the waiting kind once i made my mind up and just executed the command. Works perfectly fine. On NC30 now. Seems cool. Only bunches of log entries related to some bugs with the Whiteboard.
We are talking about CORE, right?
cd /usr/local/www/nextcloud
su -m www -c "/usr/local/bin/php updater/updater.phar"
There is no www-data user on FreeBSD. Don’t know where from you got that command line.
HTH,
Patrick
That’s good to know. I’ve been doing updates through the WebUI since Nextcloud 23.
My installation wouldn’t be considered “large” so that’s probably why I’ve been ok.
There doesn’t seem to be a difference between using the GUI and using the CLI, except for the timeout part. The actual commands would be the same I think?
Absolutely. The UI just has a good chance of running into your PHP-FPM (or equivalent) execution timeout, so using the CLI is always recommended.
Good to know. Thanks!
Why does it take so awful long to upgrade a jail?
Some jails upgrade within seconds, other have to download and apply lots of patches.
From 13.3 to 13.4. All jails come from the same version.
Because iocage in all its glory thinks you need a complete FreeBSD source tree inside your jail and also upgrades that. File by file, from git (?) not quite sure where that went after the SVN → git switch.
Anyway, check your jails before a major upgrade. If there is a /usr/src directory in there, nuke it. Then perform the upgrade.
2 Likes