crewship db operates on the local SQLite database in the configured data
directory. It does not perform maintenance on a remote server selected with
--server, a profile, or CREWSHIP_SERVER; it prints a notice when those
settings point elsewhere.
Stop crewshipd before commands that write or replace the database. The
commands are host-side operations and do not require an API session.
crewship db migration-status
Reads the local migration ledger and reports the applied schema version plus
outstanding post-deployment migrations. It is read-only and can run while the
server is stopped.
crewship db repair-ledger
Repairs a migration version collision after a migration was renumbered. It
moves ledger version numbers only; it does not change table data or schema.
--dry-run is read-only and may be used while the server is running. Applying
the repair refuses to proceed while a local server is detected. The command
fails closed when the ledger names a migration unknown to the current binary;
that case requires a newer binary or a snapshot restore.
crewship db restore-snapshot
Restores a pre-migration snapshot created beside the local database. Before an
actual restore, the current database is copied to a reversible
.before-restore-* file. Stop the server first.
--server target does not change which local file this
command operates on.