11 Replies
Project ID:
1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926,1ea2ce1e-a1e6-4445-a1b6-4e41ebfae926
tried multiple times with default var build command
npx prisma migrate dev && npx prisma db seed && npx turbo run build
changed build command and tried this in the last attempt
npx prisma migrate dev && npx prisma db seed && npx prisma generate --schema=/packages/prisma/schema.prisma && npx turbo run build
likely your absolute path is wrong since the repo is placed into an
/app
folder at the root of the container
try either prepending /app
onto the path, or try ./packages/prisma/schema.prisma
for a relative pathJust tried this now and same result, trying the first option. Any chance you could reproduce it?
I don't even know what documenso is
but this is just a case of an incorrect path
(digital document signing, docusign alternative, is more secure)
cool
when i tried to use it i also had errors and gave up (skill issue)