I had planned a next alpha release for this week, but we had some large code changes that delayed things a bit. I expect that I can release the alpha3 next week. The Alpha 3 will include the DNS-manager, so that we have almost all basic features then.
till could you also spend some time doing a quick german to english varible + strings translation for the community, i understand ispconfig is opensource, but when looking at your code its very hard to understand wants going when all the strings and variables are in german!! if you could comment your code in english or give a quick translation sheet on your string and variable names that would be great! - means i can start contributing to the project rather than hacking around bits of your code etc..
There are no variables in german in ISPConfig 3 and just one file which has german comments. I guess you mix up ISPConfig 2 and 3. ISPConfig 3 is a complete new project, written from scratch which does not share code with ISPConfig 2. In ISPConfig 2, most files are commented in german.
A Couple Questions for ISPCONFIG3 #1 will there need to be a client end of Ispconfig3 on each server? #2 would it be able to manage a windows 2000 server mixed in the farm? #3 is there a release date for a finished release? Thanks guys you guys are the best on here
1) No, there is just one client interface for all managed servers. 2) No, at least not at the moment. We will start with support for linux and then add support for freebsd and maybe solaris. 3) No. But I expect that we have a first release at the end of the year.
I have a few questions about ISPConfig3... 1:Will it support mirroring/replication of server? 2:When I create a DNS zone will it create a slave zone on another server automatically? 3:Are there any other mirroring/fail-over features going to be implemented into this version?
my question is will there be an upgrade from ispconfig2 to ispconfig3 or will it need to be a new install?
config mirroring, yes. Data mirroring can be done with e.g. rsync or a cluster filesystem and is not part of a controlpanel. All DNS is managed in a mysql databse, so there is no zone creation for slaves nescessary as all slaves run on the same or a replicated database. No, because this is something that is configured when you setup the servers e.g. by using apache mod_proxy and cluster filesystems and nothing that needs to be configured in the controlpanel.
No. Because ISPConfig 3 has other software requirements and a ISPConfig 2 setup is not compatible. There will be a import function for ISPConfig 2 settings.
So I'd need to set up the server from scratch, then import the settings and then move the data across? Sounds like a big task.
You dont have to update to ISPConfig 3, just stay with the ISPConfig 2 series if you dont want to reinstall your servers. The new features in ISPConfig 3 have other software requirements then ISPConfig 2 has.
Till, will 3 be able to support MySQL replication of the control DB? For people that start with one box, then move to two, for redundancy, this is almost a must.
Sure. But this has not to be configured in the controlpanel, just setup primary slave database replication on all servers where the controlpanel server is the master.
Third alpha version of ISPConfig 3 available for download as installer tar.fz and ready to run vmware image: http://www.howtoforge.com/forums/showthread.php?t=16962
