Skip to main content
The lstack CLI owns the installed-product lifecycle. Program files and private application data have separate locations so updates and default uninstall operations can preserve user data.

Routine operations

Check health

Inspect core health, configuration, database integrity, logs, and Docker availability.

CLI reference

Review the commands used to control an installed instance.

Updates and rollback

lstack update downloads and verifies the requested version, backs up the database, switches versions atomically, and gates the new version on health. A failed health gate returns to the previous retained version.

Backups

Create a verified SQLite snapshot with:
Backups do not modify project folders.

Uninstall

Default uninstall removes program-owned installation files and preserves application data and projects:
The --purge-data variant is destructive and requires explicit interactive confirmation. Project folders remain outside its deletion scope.