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.
I think the new list of features would be enough to want me to definatly use ispconfig, rather than cpanel or plesk or something...
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.
1) This is open source software, if you find bugs, post them or fix them yourself. 2) There is no other roadmap for ISPConfig 3. 3) ISPConfig is very stable and is used by many poeple. If you dont like ISPconfig, dont use it.
No, ISPConfig doesn't fail, except when your system doesn't fulfill the requirements. If you set up your system as described in any of the tutorials mentioned at the bottom of http://www.ispconfig.org/documentation.htm, then you will have a very stable system! There's only one roadmap, and Till posted it only once! No, it's not unstable. I'm using it in production environments every day, without any problems. Please don't blame your own errors on ISPConfig! As I said above, it is a stable software. If you find a bug, then tell us exactly what you did so we can try to reproduce the bug, post logs that show the error, tell us on what platform you are, etc. but please in a constructive way and not by making hysterical posts here!
what i had said That if i used ispconfig 2 ( post fix mail ) and comes ispconfig 3 ( Exim ) and i have at least 100 web sites with emails ? how i can transfer to another system postfix-> Exim ________ Sl175
ISPConfig 3 is not even in alpha state yet. ISPConfig 2 will not be dropped if ISPConfig 3 is released, because ISPConfig 3 has a totally different architecture. With an import script
Hi, another interessting feature might be that ispconfig is able to handle backupMX entries, means that the exim MTA can accept emails from a domain, which is not "installed" in ispconfig and relys them to the server with the next lower MX entry... Ciao PM
I know that this was mentioned above but I would like to say that having an import option to get all current version 2 customers and putting them into version 3 is a must, if you want people to use V3. Also the option to install and convert over V2 ie if your running one server with V2 on it you can just install V3 over the top and everything will be done for you... if this can be done easyily (I know its a big ask but it would make life a lot easier if this could happen). Thanks
Noone said that there wont be an import script to import settings from ISPConfig 2 to ISPConfig 3. As i posted above, the development of ISPConfig 2 will not stop when ISPConfig 3 is released. ISPConfig 3 is not a simple upgrade or some new features for version 2, its a completely different architecture and so an automatic upgrade without manually installing new services first will not be possible.
i'd imagine that if you focused too much on the import scripts, rather than the actual development of v3, that it would take much longer. you might take a lesson from vbulletin on this one... and work on the v3 release first.... and then afterwards finish the upgrade (impex) scripts for people who want to upgrade.
We have not started working on the imports scripts yet and I will start this task first when ISPConfig 3 is relaesed as Beta or RC1.
A thing that poopt up in my mind...aint it posseble to day to run ispconfig 2.x on multiply servers if you nfs the webdir and configdirs and check the config files (at the mailserver etc) and md5 check them and if they are edited, copy over it and reload it. Its a days work of scripting or am i wrong? Its a ugly way anyway
