vm VS bento

While the Hansson VM works fine and I haven't had many issues other than this, I strongly recommend to use a difference version of NC. This guy is obviously trying to scam users into paying him money for something he could easily add to his update script. Proof is here on this GitHub page, though I was unable to get it working. However that is likely a limitation of my abilities and nothing to do with being able to modify the script.

What is the difference between the All-In-One VM on the NextCloud website and those from Hansson IT? According to the GitHub page, the version on the NextCloud website is not the "full version". What does that mean? What is missing?

Yes, I've run into an occasional issue during the upgrade on the VM, but I always take a snapshot before the update so i can roll back and try again if i run into any issues. To install ffmpeg or others, you can directly install it on the VM. A simple apt-get and it'll be a persistent install (It won't be uninstalled by a NC update). The official Nextcloud VM uses ubuntu and Postgres (https://github.com/nextcloud/vm) and is pre-tuned for pretty good performance. It also has some built in scripts in the /var/scripts directory that you can use to easily install additional features and configurations, test beta releases, etc.

If you're up for another attempt, try without AIO. It is not as easy to find as it used to be, I admit, but it is there on https://github.com/nextcloud/vm. The 2 links below are found on the github page.

I'd recommend informing the devs about this via Github.

The vm says, "If your DDNS provider isn't already supported, please open a new issue here: https://github.com/nextcloud/vm/issues".

The github page has packer templates that you can modify to make your own custom boxes.

- https://github.com/chef/bento/tree/main/packer_templates/windows

I've previously used Hashicorp Packer configs in a private git repo (based on the 'chef bento' configs used for many standard Vagrant boxes) that can build template server images for and then deploy a complete fully unattended CI pipeline from scratch, using nothing more than Apache Subversion (built into CentOS and RHEL but also has an excellent Windows version!) and Jenkins. Takes under 15 mins to provision both and can be tested locally (and completely offline!) in Virtualbox as it uses a limited amount of resources. I developed the solution for a rather risk averse client that required a cheap and easy reusable centrally managed CI pipeline that could handle larger sources than git by default and be built from artefacts on a private 'air-gapped and sheep-dipped' LAN with verified SHA256 hashes for all vendor binaries. Source: https://github.com/chef/bento