Nope -- rather than compiling things, Virtualmin uses native packages.
Virtualmin attempts to use the distro's packages where possible, but in some cases custom packages are provided at software.virtualmin.com (or software.virtualmin.com/gpl).
Those repositories should be setup automatically when installing Virtualmin using the install.sh script.
Hurm, on the same track... will webmin/virtualmin just "work" if I do a manual build of apache to a later version than I currently have? Or will I have to reconfigure things. Like the vhost entries etc... or can virtualmin be told to put those back in?
Ok - can I update Apache (and so long as I backup my .conf file) can I restore it without an issue and keep working?
I've been asking on #httpd and #centos on freenode IRC and have just been advised that the version available with Virtualmin is out of date by a few securitiy exploits. Will you build a new version in the VM repo list or should I just build my own version of apache from my choice of repo.
If so, anything I should do before hand? IE: Copy httpd.conf for a backup? .. ??
If there's newer Apache versions available on CentOS, you may want to file a bug report regarding those newer versions so that they can build a newer version and get that into the repository.
You can file a report using the Support link above.
As far as how to continue to use your current config files if you install a different Apache version -- how that works all depends on the Apache you're using, and what config files/locations it's setup to use.
A few notes on that --
I'd always recommend having offsite backups of every config file on your server
Once a new Apache version is available in the Virtualmin repo, if you upgrade to it, it will re-use your current config files
If you want to compile Apache yourself -- you might consider building an RPM, using the same .spec file used by Virtualmin. You can go in there, modify the Apache version being used, and options being enabled -- but otherwise you'd end up with a similar result (which is good!).
Nope -- rather than compiling
Nope -- rather than compiling things, Virtualmin uses native packages.
Virtualmin attempts to use the distro's packages where possible, but in some cases custom packages are provided at software.virtualmin.com (or software.virtualmin.com/gpl).
Those repositories should be setup automatically when installing Virtualmin using the install.sh script.
-Eric
Yeah, I've added EPEL and
Yeah, I've added EPEL and RPMForge manually as I wanted some things not on CentOS or the Virtualmin repo's.
Be nice if Virtualmin/Webmin had the option to be able to recompile Apache - as I need to do so, so that I can attempt to resolve my crashing issue.
Hurm, on the same track...
Hurm, on the same track... will webmin/virtualmin just "work" if I do a manual build of apache to a later version than I currently have? Or will I have to reconfigure things. Like the vhost entries etc... or can virtualmin be told to put those back in?
Ok - can I update Apache (and
Ok - can I update Apache (and so long as I backup my .conf file) can I restore it without an issue and keep working?
I've been asking on #httpd and #centos on freenode IRC and have just been advised that the version available with Virtualmin is out of date by a few securitiy exploits. Will you build a new version in the VM repo list or should I just build my own version of apache from my choice of repo.
If so, anything I should do before hand? IE: Copy httpd.conf for a backup? .. ??
If there's newer Apache
If there's newer Apache versions available on CentOS, you may want to file a bug report regarding those newer versions so that they can build a newer version and get that into the repository.
You can file a report using the Support link above.
As far as how to continue to use your current config files if you install a different Apache version -- how that works all depends on the Apache you're using, and what config files/locations it's setup to use.
A few notes on that --
I'd always recommend having offsite backups of every config file on your server
Once a new Apache version is available in the Virtualmin repo, if you upgrade to it, it will re-use your current config files
If you want to compile Apache yourself -- you might consider building an RPM, using the same .spec file used by Virtualmin. You can go in there, modify the Apache version being used, and options being enabled -- but otherwise you'd end up with a similar result (which is good!).
-Eric
Submitted Bug Report!! :)
Submitted Bug Report!! :)