Running the Evolution CMS Manager on a Subdomain

This article explored a more structured variant of manager relocation: keep the main site on its normal domain, but serve the manager from a dedicated subdomain such as manager.example.com.

Why do this?

• separate frontend and admin paths more clearly
• avoid hosting-panel path conflicts
• experiment with a cleaner deployment topology

Important configuration idea

The original guide kept the main core configuration intact and instead updated the manager-side config files so the manager and connectors used their own base URLs and paths.

define('MODX_MANAGER_URL', '/');
define('MODX_SITE_URL', 'http://site.ru/');
define('MODX_ASSETS_URL', MODX_SITE_URL . 'assets/');

The guide also warned about two practical issues:

• manager-side components often assume the default path layout
• minification or bundled asset handling may need extra attention

This is still the right way to think about such moves: not as one clever config trick, but as a deployment change that has to be tested across the manager, connectors, assets, and custom components.