First, thanks a lot Till for your answer... although we both know this issue is just in the limits of ISPconfig's concerns. :-)
If I finally pass the "out of topic" line, just say it and I won't ask again.
> Do you want to pass/recover the content of your websites and databases or do you want to do this with the complete operating systema incl. all websites at once?
It need to be as atomic as a single "website"... as far as every website will content a different project. And when I say "website" I mean apache files (html, php, css...) and mysql ones because every CMS store some essential data in the DB that is an important part of what need to release (user information, form creation, text content...).
As you noticed, my English is a crap
, so just in case I didn't explain myself the scenario is very well explained here: http://www.sitepoint.com/blogs/2006/...b-development/
(although the subversion solution is just one possible approach...)
> If you want to do this just for the website data and you need versioning, have a look at SVN. I know some webdesign companies that do it this way.
Thanks. Yes, this is my first option right now... if I didn't find a simple and effective way.
The idea is installing a subversion server (in the testing machine) and when development is finished, release it to the production server in a new (or updated) ISPconfig's site.
So seams obvious that an script could be helpful... I'm asking myself if there any way to create new ISP Sites from command line. Any clue about this?
> If you do not need versioning, rsync is a good choice. Rsync can also be used to sync sites within a cluster of webservers or to make a hot standby server.
If it's easier to implement, I can start without versioning and jump to subversion further.
Instead of rsync, people is talking a lot about "unison" as a much better solution:
But once again, it's important to know what files need to be synchronized.
From my ignorance of ISPconfig I believe that an update of the /var/www/sitename and the associated DB will be enough to let the production server work with a new release, but... what will happen on new sites? Looks like production ispconfigDB also need to be updated with site creation and user accounts... but I don't know if I'm missing something else...
Finally I was really optimistic about the ISPconfig's backup utility.
May I recover a partial backup from testing ISPconf to the production one?
If I'm not been too much creative with ISPconfig uses and this is possible it will be (by far) the simplest solution and will "transform" ISPconfig to a nice staging system.
I just hope I did explained myself.
Thanks a lot in advance for your help,