Install Scripts Application Update Solution


There seems to be a fundamental problem with Install Scripts. It is, by design, perpetually out of date.

I just lost a client who heard that Joomla is “insecure”, and I was trying to make the point the Vmin lets me to mass updates, but not to the latest version.

I just did an apt-get update and upgrade so I have what’s apparently the latest Virtualmin, 3.71 Pro.

For a platform as powerful as Virtualmin is, the idea of tying script updates to Virtualmin updates seems horribly backward. Since many of these version updates are security related, it could be argued that the backwardness of this system is destabilizing or a security threat to the server.

Can’t Virtualmin be written to check some one central Virtualmin Scripts Version Master Repository somewhere? That seems simple enough to maintain.

Anyway, Virtualmin is saying that Joomla 1.5.13 is “Latest”, but it’s not, Joomla 1.5.14 is Latest.

I am sure that there are some instructions somewhere for managing this, but why does it seem like a good idea that hundreds or thousands of Virtualmin administrators have to manage versioning of dozens of applications for their particular instance? Don’t we all have better things to do? What’s the theory- that we all subscribe to the RSS feeds of the dozens of apps, and then, when a new version is announced, try to remember what the editing procedure is…

Can’t we use the machine power more wisely, and move toward self-patching systems?

Thanks for any pointers and thoughtful feedback.


This has been a long-standing issue, which is unfortunately more complex to fix than it would first appear. New script versions are often more than just a version number - in some cases, a new release may have a different install method, download website, archive format, dependencies or installation steps. So we can’t just have a service that publishes the latest version numbers…

However, I’ve been thinking about this and have come up with a method that will allow Virtualmin systems to optionally “subscribe” to new releases of the script installer code, which include new script versions and the logic needed to install them. This should be in the 3.73 release…

I know that there are complexities. I’m looking forward to seeing what you’ve come up with.

What is the anticipated timeline on that 3.73 release?

I just did a yum update, and it looks like I got 3.72


I’ve implemented a solution for this, which will allow you to subscribe to script updates at System Settings -> Script Installers -> Installer Updates. It will be in the 3.73 release …