Zero-Downtime Updates & Rollback

Self-hosted StoreConsole installs update from inside the admin panel. Updates are built by our release pipeline, checked against your licence and installed without taking the site down.

Where

StoreConsole → Updates in the admin sidebar. The page shows your version, the latest available version, the release notes and an Update button. Progress survives a page reload, and a second update cannot start on top of one already running.

What happens when you click Update

A snapshot is offered first. Take it.
The new release is downloaded and unpacked beside the live site, in its own directory.
Database migrations run, and the new release is test-loaded.
The site switches to the new release in one step. The application cache is cleared once, right after the switch.
Release-specific setup runs once and is recorded, like a migration, so settings you changed are never overwritten by an update.

The site pauses only when a release changes existing database columns, and only for that step.

Rolling back

The last two releases stay on disk.
Switch back from Updates → Releases, or run php artisan launcher:release:rollback.
Rollback switches the code only; the database is left as it is. If a release changed data you need back, restore the snapshot you took before updating.

Installs without release directories

Some shared hosts (for example cPanel without symbolic links) cannot use release directories. They keep the in-place update. Run php artisan launcher:release:adopt on a server that supports it to convert an existing install.

If an update fails

Do not start another update. Read the message on the Updates page.
Check that the queue worker and scheduler are running and that disk space is free.
Use rollback to return to the previous release, then contact support with the message shown.

Zero-Downtime Updates & Rollback