MODx Revolution multi domain installation tutorial

Quote from: odeclas at Feb 07, 2011, 12:06 PM

For my dev site (with multiple client sites) I simply have one manager / packages install, and several contexts that point to subdomains / physical folders. I then create site-specific categories to keep my elements / chunks clean (with a custom mnemonic prefix for each client).

It’s kept me sane during the eight? manager upgrades that have been made since June... and countless package updates. I now make it a policy to only upgrade to -pl packages (although only Shaun is really strict on that naming convention).

Now, if only I could persuade my clients to all use the same host....

Are you using a plugin to direct users or doing it with index.php? Any virtual hosts involved?

FWIW, many of my packages should probably be listed as pl (or at least rc). I’ve just been to lazy to change them.

That would include captcha, spform, thermX, ezFAQ, and Personalize. NewsPublisher and MyComponent are true betas and ActivationEmail, and QuickEmail should probably be considered RC. There’s a long tradition in MODx of designating fairly robust add-ons as Beta versions.

I don’t use a plugin or vhosts. I simply have

www.domain
- has the core, manager and packages
cl1.domain
- at /cli1/
- has its own assets folder, index.php, .htaccess (not sure if this is really required) and a config.core.php that points at the master
- I then set all I need to change at the context level
cl2.domain
- at /cl2/
- has its own assets... etc

What doesn’t work in this setup is I can’t access cl1.domain/manager or cl2.domain/manager etc - but then again I don’t need/want to for dev purposes.

Good tutorial!