Skip to main content

Upgrading Liteset

Docker Compose​

Shut down the running containers:

docker compose down

Update the folder that mirrors the liteset repo through git:

git pull origin main

Restart the containers — any changed Docker images will be pulled automatically:

docker compose up

Updating Liteset manually​

To upgrade Liteset in a native (PyPI) installation, run:

pip install liteset --upgrade

Upgrading the metadata database​

Liteset's Alembic migrations are run with the sync psycopg2 driver. Migrate by running:

superset db upgrade
superset init

These commands are identical to Apache Superset and the Alembic revision graph is shared — an existing Apache Superset metadata DB upgrades cleanly under Liteset.

While upgrading Liteset should not delete your charts and dashboards, we recommend following best practices and backing up your metadata database before upgrading. Test the upgrade in a staging environment before production, and prefer off-peak usage windows.

Migrating from Apache Superset to Liteset​

Because Liteset preserves the metadata DB schema, REST API, session-cookie format and SPA frontend of Apache Superset 6.0.0, migrating an existing installation is a backend swap:

  1. Stop Apache Superset (docker compose down / systemctl stop superset / etc.).
  2. Take a snapshot/backup of the metadata DB.
  3. Install Liteset (pip install liteset or pull the Liteset Docker image).
  4. Point Liteset at the same metadata DB and Redis.
  5. Start Liteset under Uvicorn — see configuring-superset.

No superset db upgrade step is required if both versions are 6.0.0 — the schema is identical. If you are migrating from an older Apache Superset, run superset db upgrade once to bring the schema to 6.0.0, then start Liteset.