How ebox platform differs from webmin?

ebox tries to provide a higher abstraction layer for the system administrator. It's meant to be easily used by users who have never administrated a Unix system before.

We have tried hard to integrate the different modules to make it work smoothly. It provides a uniform interface and a tight integration amongst the modules. For example, when you enable the HTTP proxy, the module will add the necessary firewall rules to make it work. Another example of integration is, for example, when you define a network object -an abstraction for an IP or group of IPs-, this object can be used across the different services. And if this object is modified, the framework will tell all the modules using it that it's has changed so that they can modify their configuration files.

It does not read the configuration back from the service configuration files, as the configuration is stored in an intermediate xml file. This means that if the administrator modifies the configuration file of a service, the changes will be overwritten by ebox. So if you ever need to log into the machine to modify something, report a bug to add a new feature :)

From the developer's point of view, ebox is a complete framework to help and minimize development effort.

It isolates the presentation layer from the module's logic, which makes easy to modify the user interface without touching the controller/model.

It extensively uses object oriented programming and some design patterns.

~

:wq