Developing new site on same server as current site

Hi,

I’ve volunteered to help my child’s school get better at regularly updating their website. Currently, it’s maintained on a different server in a *very* simple php script. We will move the site to a new server soon. Naturally, I’ve pushed for using Modx as back-end, since this will make updating the site a breeze.

I’ve got two options for development. The original site will be installed in the root of the domain (and will still be live).

• Develop on a different server. When done, copy database and all files to the new server, effectively overwriting the original site (note to self: make a backup!).
• Install Modx in a sub-directory on the new server. When done, move all files to the new server root folder (thanks ganeshXL), effectively overwriting the original site (note to self: make a backup!).

Which is the preferred method? Or is there a third method, far better than these two?

Thanks.

I expect your existing site is using index.php as the entry point so this wouldn’t work.
If it weren’t or for the sake of illustration it was a static HTMlL site :
Install MODx along side, develop, test, client approves, archive existing site, turn on FURL’s, job done.

Quote from: bunk58 at Oct 03, 2008, 03:26 PM

I expect your existing site is using index.php as the entry point so this wouldn’t work.

It is using index.php, but why wouldn’t this work?

MODx would use index.php, so the current site would disappear if you used the MODx index.php file.

Quote from: bunk58 at Oct 04, 2008, 02:32 PM

MODx would use index.php, so the current site would disappear if you used the MODx index.php file.

But if I have Modx currently in a sub-directory, where it’s index.php resides, how would that affect the index.php in the root?

Quote from: sderuiter at Oct 04, 2008, 02:35 PM

But if I have Modx currently in a sub-directory, where it’s index.php resides, how would that affect the index.php in the root?

It wouldn’t if you install MODx into it’s own sub-directory, it would only cause issues if you install alongside your current site at the root level. When moving, just take a backup of the current site first, remove the current site files or demote them to another folder, and then shunt MODx to the root level.

Don’t forget that if you install MODx into a sub-directory for development, you’ll probably need to check through the MODx system configuration settings when you’ve moved it to the root level as there’s a few settings (file manager path being one of them) that will probably need their paths adjusting to reflect the move.

Aside from that, installing into a sub-directory is probably the easiest way to do it.