Submitted by beat on Wed, 06/10/2009 - 09:54
Hi Jamie,
You removed old tracker before we downloaded the installed .pl file for Joomla 1.5.11 security release for VirtualminPro 3.69Pro...
We really need it.
Sorry to bother you about that, but don't find that tracker item ported into the new tracker.
Many Thanks, Beat
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Wed, 06/10/2009 - 11:36 Comment #1
I have attached the Joomla 1.5.11 updated installer to this bug report..
Submitted by beat on Wed, 06/10/2009 - 12:00 Comment #2
Thank you Jamie :)
Jamie, if the script API has mostly stabilized, this is something we probably ought to have an automatically updated (from SVN) repository for. Something in software.virtualmin.com. It wouldn't need to roll out to users automatically yet, but we could add an index of available versions to the website somewhere.
Submitted by beat on Wed, 06/10/2009 - 16:38 Comment #4
Probably a real virtualmin module would do fine to have updates sooner, but most importantly independantly from Virtuemin release cycles...
Or have a local cache like with packages and a once-a-day update try.
BTW: Where to put that file ? - I had that info on old tracker, but not finding it anymore.
Submitted by JamieCameron on Wed, 06/10/2009 - 16:42 Comment #5
I think it is pretty stable now.
We could either have a separate package for scripts that we could release more often, or allow easier updates of script .pl files from SVN as you suggested.
I like the first option, as we already have all the code to support it. The only tricky part would be migrating existing users, who would have to install the new virtualmin-scripts package. But this could be made an RPM or Debian dependency in the repos..
You can add scripts in the Virtualmin UI in System Settings>Script Installers>Add Script.
Or you can drop it into /usr/libexec/webmin/virtual-server/scripts on CentOS or /usr/share/webmin/virtual-server/scripts on Debian.
Submitted by beat on Wed, 06/10/2009 - 16:51 Comment #7
Very cool :) Looking forward :)
So, we'd package /usr/libexec/webmin/virtual-server/scripts separately? Does a .wbm module allow for module installations nested like that?
And, yes, we can add a "Requires: wbm-virtual-server > 3.70" or whatever to the RPM to enforce matched versions, and add the wbm-virtual-server-scripts module to the virtualmin-base dependency list. Since we'll be doing 3.70 soon, it'll have to wait until 3.71. But, assuming .wbm can deal with a nested module like that, I'm down with the change happening after the next release.
Then again, since it currently takes about an hour of human time to roll a new package across all platforms...maybe having it update via simple files would be preferable. But, no, I guess it's just time to finally finish automating releases completely and get a snapshot+build system running. Now that I have Cloudmin, I can spin up the instances I need via a script and shut them down when finished. No need for humans to be involved at all. ;-)
Submitted by JamieCameron on Wed, 06/10/2009 - 19:19 Comment #9
I was thinking a new RPM, for a module called virtualmin-scripts, which would be a plugin that provides all the current scripts to the core Virtualmin module. All the existing scripts would then be moved to this new module. That way there would be no need for overlapping modules, which Webmin doesn't really support.
Also, the wbm-virtual-server package could have a "Requires: wbm-virtualmin-scripts" line to ensure that when it gets upgraded to a new version that doesn't have scripts, the plugin that does gets automatically installed..
Isn't that what I just said? ;-)
Or are you meaning move them to /usr/libexec/webmin/virtual-server-scripts?
Or, rather /usr/libexec/webmin/virtualmin-scripts
Submitted by Issues on Sun, 06/28/2009 - 01:25 Comment #12
Automatically closed -- issue fixed for 2 weeks with no activity.