ISPConfig Roadmap

[till]

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.

[falko]

Originally Posted by hadisaadeh

i see that these systems will fail ?
why /

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!

Originally Posted by hadisaadeh

i see that every day you put road map diferrent from the old system
why ?
unstable system

There's only one roadmap, and Till posted it only once!

Originally Posted by hadisaadeh

i see that system is good
but unstable like cpanel?

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!

Originally Posted by hadisaadeh

there is many faults

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!

[hadisaadeh]

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

[till]

Originally Posted by hadisaadeh

That if i used ispconfig 2
( post fix mail )
and comes ispconfig 3
( Exim )

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.

and i have at least 100 web sites with emails ?

how i can transfer to another system
postfix-> Exim

With an import script

[pontifex]

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

[mphayesuk]

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

[till]

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.

[Bailx]

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.

[till]

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.

[lerra]

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