Non-existent file mentioned in the documents

Open Beginner friendly
#33 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active

Research direction

Review the Running on Supabase and Running on Vercel guides, then inspect commit 88639dfe83a93d2314b011e267e2344aad615361 and the current prisma/schema.prisma. Verify which schema changes the deployment instructions require, update both documents to use the valid path and instructions, and confirm the referenced file and steps are consistent.

Written by the indexing model from the issue text.

Description

Hi,

I believe on master branch, db/postgresql/schema.prisma no longer exists; instead, it was moved in commit 88639dfe83a93d2314b011e267e2344aad615361 from August 14, 2025, and is now prisma/schema.prisma.

However, in the document Running on Supabase and Running on Vercel, it still mentions to do changes on db/postgresql/schema.prisma .

If anyone knows how it should be, could you please update the documents?

I'm trying to host Umami on Vercel and not sure if I shall apply the same changes. I haven't looked into the changes on prisma/schema.prisma after that relocate commit. I'll later spend some time tracing it or do it by trial and error. I will create a PR if I'm certain about what changes shall be made.

Dominant language
MDX
Stars
5
Forks
24
Avg merge
3d 14h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from umami-software/docs

All issues in umami-software/docs

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.