Upgrading & Migration

Version upgrades, database migration, and rollback procedures.

Version Upgrades

Bare Metal

curl -fsSL https://www.nobacmd.com/install.sh | bash

The installer handles dependency updates, frontend builds, and service restarts. SQLite schema migrations run automatically on startup.

Docker

curl -fL https://www.nobacmd.com/download/latest/docker-install.sh | bash
docker compose up -d

The install script downloads a SHA-verified image tarball from R2, loads it into the local Docker daemon, and tags it as noba-enterprise:latest. Pin a specific version with NOBA_VERSION=…. SQLite migrations run automatically when the container starts.

Self-Update (from the UI)

Navigate to Settings → General → Self-Update and click Check for Updates. The built-in updater pulls changes, verifies integrity, installs new dependencies, and restarts — with automatic rollback on failure.

Database Backend Migration

NOBA supports three database backends: SQLite (default), PostgreSQL, and MySQL/MariaDB. You can migrate from SQLite to either relational backend at any time.

SQLite → PostgreSQL

1. Create the PostgreSQL database: createdb noba
2. Install the driver: pip install psycopg2-binary
3. Initialize schema: python3 scripts/init-postgres-schema.py
4. Migrate data: DATABASE_URL=postgresql://... python3 scripts/migrate-to-postgres.py
5. Stamp Alembic baseline: noba-migrate stamp 001
6. Apply pending migrations: noba-migrate upgrade
7. Set DATABASE_URL and restart NOBA

SQLite → MySQL / MariaDB

1. Create the MySQL database with utf8mb4 charset
2. Install the driver: pip install PyMySQL DBUtils
3. Initialize schema: python3 scripts/init-mysql-schema.py
4. Migrate data: DATABASE_URL=mysql://... python3 scripts/migrate-to-mysql.py
5. Set DATABASE_URL and restart NOBA

Schema Versions

Rollback

Bare Metal

cd ~/noba-enterprise
git log --oneline -10          # find the last known-good commit
git checkout <commit-hash>
bash install.sh --upgrade

Database

Before migrating backends, NOBA creates a backup automatically. You can also create one manually from Settings → Database → Backup.

For PostgreSQL downgrades: noba-migrate downgrade <revision>