Deploy and rollback

A deploy brings a defined state to your hosting: a core version plus a state of your overlay plus the configuration.

1. The control center builds core release (for example v0.3.0) and the chosen state of your site repository.
2. Transfer via rsync over SSH (only changed files) or SFTP.
3. config.php is written separately with mode 600. var/ and public/media/ stay untouched.
4. The site then runs migrate, katalog and cache-leeren.

Core files are read only on the server. Checksums let the status job report changes to the core, which raises an alert.

History and rollback: every deploy is listed with core commit, site commit, file count, author and duration. Roll back rebuilds exactly the state of an earlier deploy and deploys it. Database content such as products and prices is kept.

Your overlay: templates in site/templates/, your CSS in site/assets/css/eigen.css, hooks partials/eigen-kopf.php and partials/eigen-vor-fuss.php, modules in site/modules/. Every change is a Git commit.

Preview check for MCP deploys: PHP syntax check with your host's PHP version, template and CSS checks, build into a preview directory outside the web root and rendering of home, category, product and error page against the real database. If anything fails, nothing goes live.