Client Maintenance
Regular maintenance reduces failures after settings, template, and version changes.
Maintenance mode
Before an update or migration, enable maintenance mode separately for the website and cabinet in project settings. Allow the administrator IP, upload the changed configuration, and disable the mode after work is complete.
Clearing cache
Use the cache clearing section in the local client admin. The equivalent console command is:
$ php cmd.php cache:clear
Clear cache after restoring files, changing templates outside the editor, or fixing stale generated data. Do not delete all of internal_data; it also contains persistent installation data.
System health check
Open System Health in the Tools section of the local client admin. This page checks the database connection, required PHP extensions, writable runtime directories, and the background job queue.
Use Run file check to compare installed application files with the checksums from the official release. Restore missing or modified system files through the regular updater or a backup. Project data and local user files are not part of this check.
Monthly checks
- perform a test restore of a recent backup;
- check update availability and runtime requirements;
- verify HTTPS and protection of private directories;
- review application and web server errors using the troubleshooting guide;
- revoke obsolete installations in the project card.