Move or relocate a site
Run Micro CMS from a subdirectory, serve it at another public path, or coexist with a legacy site during migration.
The folder containing Micro CMS does not have to be the same as the public address visitors use. This is useful when replacing an existing site gradually.
Public and Admin addresses
Set the public address to where visitors should reach the site. Set the Admin/control path to the location used to manage the installation. Use the Site Settings fields rather than adding server-specific folder paths to content.
Coexist with an existing site
During a migration, your web server can keep the existing site available while sending the routes you have moved to Micro CMS.
Apache example
RewriteEngine On
RewriteRule ^$ /cm/index.php [QSA,L]
RewriteCond %{REQUEST_URI} !^/cm(?:/|$)
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^ /cm/index.php [QSA,L]This example assumes Micro CMS is installed under /cm. Change the path to match your installation and test it on a staging site first.
Legacy fallback
If you are using the built-in legacy-site fallback during a migration, configure the existing site's entry point in the supported deployment setting and enable Legacy fallback in Site Settings. Disable it once the cutover is complete.
Bridge Silos on paths
A Bridge Host can serve supported Silos from different paths on the same hostname, for example /, /test and /mc. Configure those bindings in Bridge and make sure the web server passes those public requests to Micro CMS.