Installating MODx on server with multiple databases

Quick question - does anyone know when your installing MODx to a server with existing non MODx databases if the new install touches the existing databases? I’m guessing not, but by the language on the install screen it makes it sound like it would: "Install a new copy of MODx Please note this option may overwrite any data inside your database." Thx in advance.

No, it will only overwrite an existing MODx database.

Thanks Patrick.

Might be a benefit if that line in the install was changed to something like:

"Install a new copy of MODx. Please note this option may overwrite any existing MODx data inside your database."

Or unless I’m the only chuckle head that was confused by that

When you run the installer, the config file is written with the connection details to a single, specific database, so whether data is overwritten depends on if you supply the same database information. You cannot use a single install of MODx 0.9.x to run multiple databases; you would need to install one instance for each database so it had it’s own config file, etc.

MODx 2.0 (a.k.a. Revolution) will be supporting multiple "named" configurations from a single "core" install, as well as many other multi-site scenarios, but it is currently in the final phases of alpha development.

Quote from: OpenGeek at Mar 25, 2009, 10:43 AM

When you run the installer, the config file is written with the connection details to a single, specific database, so whether data is overwritten depends on if you supply the same database information. You cannot use a single install of MODx 0.9.x to run multiple databases; you would need to install one instance for each database so it had it’s own config file, etc.

MODx 2.0 (a.k.a. Revolution) will be supporting multiple "named" configurations from a single "core" install, as well as many other multi-site scenarios, but it is currently in the final phases of alpha development.

That makes sense, thanks for the input OpenGeek