Dear Till, I know you're busy with the developement of ISPConfig 3.0. This version will support multiple servers which is very nice. Is it maybe an idea to install php as a CGI, so we can use suPHP as default in combination with ISPConfig? I think it is a professional solution, which is also used by the bigger hosting companies. Another nice feature would be that forwarded email is scanned for (virusses and spam) first, before it is forwarded to an external mailaddress.
It's also a major force driving customer to me Hans. php cgi is slow and has problems of it's own. Perhaps have it as an option, but forcing it would mean I wouldn't be able to use version 3. In my opinion, PHP as CGI is a waste of resources.
Awesome Till. I love options. Hans, sorry for my tone, wasn't trying to dismiss PHP as CGI, more that it really should be a option and not forced. I really worded things badly there.
No bad feelings here I like to hear your opinion! Personally i prefer php as a module for "normal"websites and php4 as CGI+suPHP for Content Management Systems for example. But the web admin must be careful with setting permissions of course.
That is where being multi-server will be an asset. You could have wildly different servers based on what a client needs. (even if the servers are VPS.)
When you guys say multi server, do you mean you have 1 master install of ISPC on a server, and the other servers have a client install. Then the master ISPC sends commands to the client servers that listen on a specified port that can then in turn create sites etc? Or do you mean multiservers as virtualisation on 1 machine? Having open ports can be a potential problem on other machines if its not ipfw/ipchains ip access control based for the open port. I hope this multiserver function is a option and not a necessity for IPC3.
ISPConfig 3 will allow single and multiserver setups. This means all services may be on the same server like in ISPConfig 2 or the services may be spread to several servers and also there may be several servers of every type, e.g. 5 webservers, 2 mailservers, 1 database server that are controlled from within one controlpanel. There where no commands send from one server to the others and there is no security problem with this. ISPConfig 3 uses either one central database server or replicated databases on the child servers. MySQL is able to encrypt the connections and if thats not secure enough for you, you may even setup mysql trogh a ssh tunnel or vpn.
Now that's a sweet sounding panel right there. And all of this is still going to be free? No "you need to go pro" licensing fees? Man you guys rock
Ahhh now I understand how you guys are designing it. That's pretty smart, I never thought of it working that way. Yeah that's not a problem at all then.
Re: Release Date When is the expected release date? If you need Beta Testers I would be awful glad to help with that I have 3 servers right now. See ya, TexasTaz
There is no release date yet. I hope that I may release a first alpha version soon. I will announce this in the forum, so everyone is invited to test it
Sounds good. I got Debian 3.1/4.0, Ubuntu 6.06/6.10/7.04, Fedora Core 6, and Centos 4.4 servers that are free to test it on .
Yes, I think we will have a beta of ISPConfig 3 until october. Yes. Not only a new design, ISPConfig 3 is rewritten from scratch and as a completely new ajax based interface.
I hope Plesk have long time for update the software for Debian Etch. My Co-Admin want Plesk on the server. He like the frontend and think the say Plesk is on most server in Internet install.I don't change from ISP Config to plesk. My personal + Points for ISPConfig is 1. Support from ISPConfig is very good 2. ISPConfig is OpenSource 3. Direct Contact to the Developments 4. HowToForge have many Howtos for Linux and ISPConfig
