Fresh DB setup fails due to incomplete Prisma migration history

[traitor09]

Summary

The repository is missing the initial baseline migrations that create core tables. This issue blocks fresh project setup and affects all new contributors.

Contexts

IN COMMIT 9d85157

The two base migration files that originally initialized the database structure were deleted: -

1. /migrations/20260312125106_init/migration.sql
   which created the core tables like users, cards, platform_links, etc.
2. /migrations/20260312162249_analytics_models/migration.sql
   which created card_views and follow_logs

CURRENTLY-
Only remaining migration file in the project - migrations.sql

It was generated to migrate a database that already had the base tables applied.

Expected Behaviour

• Fresh install should create full database schema successfully using Prisma migrations.

Recommended Fix

• Creating a single new baseline migration

Restoring the deleted init and analytics_models migrations alone would still leave the database schema inconsistent with schema.prisma.
The schema has evolved (e.g., new Card fields like description, slug, visibility, qrEnabled, viewCount) without corresponding migrations, and these changes are not reflected in any existing migration files.

This would still require manually reconstructing missing SQL changes or dealing with schema drift between Prisma schema and migration history.

Area

backend

Steps to Reproduce & Error Message

See the steps to start backend

❯ npm run db:migrate

> devcard@1.0.0 db:migrate
> npm --prefix apps/backend run db:migrate


> @devcard/backend@1.0.0 db:migrate
> prisma migrate dev

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "devcard", schema "public" at "localhost:5433"

Error: P3006

Migration `20260617074743_refresh_token_cleanup_indexes` failed to apply cleanly to the shadow database. 
Error code: P1014
Error:
The underlying table for model `users` does not exist.

[github-actions]

👋 Thanks for opening your first issue, @traitor09!

We appreciate your contribution and are excited to have you here. Please make sure to follow the contribution guidelines and provide as much detail as possible.

To stay updated, ask questions, and connect with maintainers and contributors, please join our Discord community:
https://discord.gg/QueQN83wn

Looking forward to collaborating with you!

[github-actions]

Hi @traitor09,

Thanks for opening this issue.

Please reply with one of the following areas so the issue can be routed to the appropriate team member:

- /backend
- /web
- /mobile
- /devops

Once an area is selected, the corresponding label will be added automatically.

[traitor09]

/backend

[github-actions]

The issue has been classified as backend.

@Harxhit, please review and triage this issue when available.

The backend label has been applied and the issue has been routed accordingly.

[Harxhit]

@traitor09 I have assigned this issue to you.

[traitor09]

Thanks @Harxhit I’ll look into it and try to submit a PR soon.

[ShantKhatri]

Hi @traitor09 , the failure you have added is from your local? Or from our workflow?

[traitor09]

Hi @ShantKhatri,

The error I included in the issue is from a fresh local setup.

I cloned the repository, configured the database, and ran npm run db:migrate on a clean database.
Prisma fails while applying the later migration because the initial migrations that create tables like users are missing from the migration history, so the shadow database doesn't contain those tables.