v1.1.1 — Database migration hotfix
Issue
Crash on startup for existing installations: the ip column on the ManagedHost model was present in the Prisma schema but missing from the db-migrate.js startup script. Any query involving connections would immediately fail with:
Error: The column main.ManagedHost.ip does not exist in the current database.
Fix details
- Added
ipcolumn to theCREATE TABLE IF NOT EXISTS "ManagedHost"statement (new installations) - Added
ip,descriptionandtagsto the additive migration list so existing databases get the columns automatically - Synced
schema.migrate.prismawith the main Prisma schema
Action required
None — the fix applies automatically on the next container restart via ALTER TABLE ADD COLUMN.
Full Changelog: v1.1.0...v1.1.1