Muhammad Ibrahim 766d36ff80 fix: migration to properly drop unique index on friendly_name ...

The migration was dropping the constraint but not the underlying unique index.
In PostgreSQL, unique constraints and unique indexes can exist independently.
This caused auto-enrollment to fail with 'unique constraint violated' errors.

Added explicit DROP INDEX statement to ensure the unique index is removed,
allowing duplicate friendly_name values while machine_id remains unique.

2025-10-04 10:44:06 +01:00

..

migrations

fix: migration to properly drop unique index on friendly_name

2025-10-04 10:44:06 +01:00

schema.prisma

feat: Implement machine_id based host identification

2025-10-04 09:02:56 +01:00