<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>In The Box - Latest Comments in Webmin::API: Using Webmin as a library</title><link>http://inthebox.disqus.com/</link><description></description><atom:link href="https://inthebox.disqus.com/webminapi_using_webmin_as_a_library/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 18 Dec 2008 01:07:13 -0000</lastBuildDate><item><title>Re: Webmin::API: Using Webmin as a library</title><link>http://inthebox.webmin.com/webminapi-using-webmin-as-a-library#comment-4475898</link><description>&lt;p&gt;Hello Joe,&lt;br&gt;thank you for webmin/virtualmin -great software and what's more important - pretty reliabel and predictable.&lt;br&gt;This perl-API is a great thing, though unfortunately it doesn't seem to help to manage webmin configuration itself. We have bunch of servers that are running various versions of webmin as web control panel for customers. I was thinking for the following scenario:&lt;br&gt;Put together a script with perl-API that upgrades webmin to the latest version + deletes modules that of no use and confuse the customers (+ may be install virtualmin/GPL + virtualmin theme + configure some virtualmin parameters along the way + may be import a bunch of legacy virtual hosts into virtualmin). Still can't figure out if this is possible to script form command line. Any suggestion will be greatly appreciated.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">al3xxx</dc:creator><pubDate>Thu, 18 Dec 2008 01:07:13 -0000</pubDate></item></channel></rss>