On Fri, 2005-04-15 at 08:18 -0700, Bill Shupp wrote:
I would prefer not to have the service management available through Vega... I give my end users access to VegaDNS I wouldn't want them to have such control...
It would be permissions based. The idea was this:
VegaDNS can administer all aspects of DJBDNS. Add/Remove which IPs it listens to, maintain dnscache settings, etc...
Of course, this would be permissions based. But the idea was to make djbdns so easy to administer, that it would encourage more people to switch to it. But I certainly have the same reservations about allowing such changes to be done over the web. That's why it has not been a priority, and I'm not sure that it ever will be.
An inherent service monitoring tool wouldn't be so bad. I'm already using spong though to monitor servers.
Segregating these functions into a companion tool is not a bad idea...
Why would you want to add/remove services from a running server,
especially production? It would make sense for a general network/server
administration tool that allowed you to provision services to servers or re-provision them as needed, but you would probably want to include
FTP, HTTP, and email administration if you were working on such a tool.
Perhaps. I'm not personally interested in managing all my services from a web interface. However, as the designer of a djbdns web interface, I thought it would be interesting to go the full distance with that application only.
It would be nice to have such a tool and an intuitive control panel in
the vein of VegaDNS for all of these things.
but inter7 I think is already on that ball with vHostAdmin, but I still haven't found an admin tool that does it all well, even on the commercial market.
The emulation of SquirrelMail's plugin architecture in vHostAdmin is a smart move, and could prove it a pretty popular tool in the long run. I'm looking forward to seeing how it develops.
Regards,
Bill
