I have several mysql databases that belong to sites but were made with other tools than ispconfig. Is it possible to retrospectively include them in an ispconfig site configuration? THis would make migrating the installation much easier (they would migrate with ispconfig migrate tool rather than each one having to be migrated manually). Thanks
The ISPConfig Migration Toolkit currently only support ISPConfig 2 and 3, 3.1 and 3.2, Plesk 10 – 12.5, Plesk Onyx, CPanel or Confixx 3. If you have normal mysql databases for example for a wordpress installation on a host that does not use one of the software above to manage the server than you have to manually dump the database, create the database and user aswell as the websapce in your ISPConfig installation and then import the database dump into the newly created one and copy over all webspace files. In many cases it is necassary to manually edit some files for example the configs that define the database connection after a migration anyways. With some sites/software more manual intervention is might needed. I've manualy migrated over 80 webspaces with databases in the last few month and some CMS systems are just a pain to copy over...
I have ISPConfig installed already and used it to setup the sites but some of the databases (all wordpress ones) I setup using PHPMyadmin initially rather than in ISPConfig, so they are not included in ISPConfig's site definitions. I was just wondering if there was a way to 'hook' them into an ISPConfig site ... I have gone the manual roiute many times before and am just looking for short-cuts (as well as being prepared for the next time I have to migrate my ISPConfig...
I was able to manage this with pre-existing databases even pre-existing users. However you should know it's risky and requires playing with either prefixes in web interface System / Main Config or manually changing contents of ispconfig database. Luckily, if database or database user exist without the prefix, ISPConfig won't mess them up (at least it did not when I tried 1.5 years ago) ...better backup your database first.