Docs Navigation Open

Deployment

Move a site between environments by transferring files, database, paths, and config in a controlled order.

Deployment means moving both the application and the content state into a working target environment. In Evolution CMS that usually means files, database, paths, and cache.

Typical Deployment Steps

verify the project locally or in staging
prepare server configuration and writable paths
upload project files
import the database
adjust environment-specific settings and URLs
clear cache and test manager + frontend

Common Problems

wrong database credentials
incorrect rewrite rules
broken file or media paths
missing published assets from packages
permissions too strict or too open

Good Practice

Deploy from a known build, not from a random local folder. Keep package migrations, published assets, and environment notes part of the deployment checklist.

Updating Evolution

Update carefully: back up first, preserve customizations, run the updater, and verify the install is closed again.

Caching

Use resource and snippet caching deliberately, and remember to disable or clear cache during active development.