ISPConfig Roadmap
 

Here is my idea of an ISPConfig roadmap. Please feel
free to comment it and post your Ideas.


ISPConfig 2.x releases

- Support for new linux distributions like Gentoo, Slackware etc.
- Smaller feature and usability enhancements



ISPConfig 3.x releases

The ISPConfig 3.x series will be a major rewrite of the application
to solve many problems that cannot be solved with the current framework.

- Switch from a config file based approach to configure the daemons
to a SQL database backend. This will improve scalability of the
application and makes it possible to manage more than one server
with the controlpanel.

My idea is to build this around the following programs

Mailserver: exim as default.
Why? Exim is easier to configure and install then postfix e.g. no SASL needed for smtp
auth, maildrop not needed for sql based mailquota, for SQL based autoresponders i
have not found a solution for postfix at all (please correct me if you know one).
As alternative postfix with SQL, but postfix needs much more
helper programs and system configuration to work. And when you look at the forums
you can see which problems this often causes even if the howtos are used.
For exim only one binary and one config file is needed for all the functionality
(OK, and a start script ;) )

Webserver: Apache2

DNS-Server: DJBDNS
Are there any better and stable SQL based DNS servers available?

Database Server: MySQL as default
Also support for Postgres, Firebird will be nice.

FTP Server: ProFTPD and maybe pureftpd


Global changes in how ISPConfig works:
------------------------------------------------------------------

- separate Email, FTP and Shell user accounts.
- You can select for each website on which server it is hosted,
same for email domains. Email and Websites can be on different servers.
- Email accounts are separaeted from websites, you can have email
only accounts.

And many other of the feature requests from the forum ... :)

Till

How about a way to interconnect more than one server running ISPConfig.

You will hate me for saying this but like the way that Active Directory can replicate to other servers in case one of the servers dies. Granted keeping a copy of the customer web data is asking too much and will take up too much space, but keeping a copy of the customer account details and passwords ect... would be very handy.

This can be achieved with the new Setup and this is one of the reasons why i chose the mysql based way. When all the configuration data is stored in the database, you can use the MYSQL database replication features to "clone" the setup. The new framework for ISPConfig that I'am currently working on has also a feature that i named datalog, it logs all changes of the mySQL database and can replay these changes to one or more external databases without needing the mysql replication faetures. The administrator can use the datalog also as an unlimited undo function if enabled.

Both ProFTPD and PureFTPD, Exim, and MRTG is what I would love to see in this Control Panel.

Hi,
and when will the new version be avail?

Ciao
PM

There is no release date yet. It depends on the number of developers.

I think the new list of features would be enough to want me to definatly use ispconfig, rather than cpanel or plesk or something... :cool:

give me a reply
 

Dear All
Who said that ?
ispconfig 3

is from the association ( ispconfig administrators ) or not ?
is that really

please reply asap
________
Extreme q

What is your question?

I've posted the ISPConfig 3 roadmap and yes, I'am one of the core developers from projektfarm GmbH, the company behind ISPConfig and 42goISP.

i see
 

Why you make that ?
older systems differs from newer ?


regards
________
Roor bong