starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 01:06:06 +03:00

[GH-ISSUE #9500] documenso prisma deploy error #2091

New issue

Closed

opened 2026-02-26 12:51:16 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 12:51:16 +03:00

Owner

Originally created by @tobiswdec on GitHub (Nov 29, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9500

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

documenso

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/documenso.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-17-pve)

📝 Provide a clear and concise description of the issue.

Script exit with fatal error

🔄 Steps to reproduce the issue.

default options with verbose

❌ Paste the full error output (if available).

[...]

@documenso/remix:build: created build/server/hono in 18.1s
[Build]: Done in 84 seconds

Tasks: 3 successful, 3 total
Cached: 0 cached, 3 total
Time: 1m33.936s

@documenso/root@2.1.0 prisma:migrate-deploy
npm run with:env -- npm run prisma:migrate-deploy -w @documenso/prisma

@documenso/root@2.1.0 with:env
dotenv -e .env -e .env.local -- npm run prisma:migrate-deploy -w @documenso/prisma

@documenso/prisma@0.0.0 prisma:migrate-deploy
prisma migrate deploy

warn The configuration property package.json#prisma is deprecated and will be removed in Prisma 7. Please migrate to a Prisma config file (e.g., prisma.config.ts).
For more information, see: https://pris.ly/prisma-config

Prisma schema loaded from schema.prisma
Error: Prisma schema validation - (get-config wasm)
Error code: P1012
error: Environment variable not found: NEXT_PRIVATE_DIRECT_DATABASE_URL.
--> schema.prisma:24
|
23 | url = env("NEXT_PRIVATE_DATABASE_URL")
24 | directUrl = env("NEXT_PRIVATE_DIRECT_DATABASE_URL")
|

Validation Error Count: 1
[Context: getConfig]

Prisma CLI Version : 6.19.0
npm error Lifecycle script prisma:migrate-deploy failed with error:
npm error code 1
npm error path /opt/documenso/out/packages/prisma
npm error workspace @documenso/prisma@0.0.0
npm error location /opt/documenso/out/packages/prisma
npm error command failed
npm error command sh -c prisma migrate deploy

[ERROR] in line 82: exit code 0: while executing command $STD npm run prisma:migrate-deploy

🖼️ Additional context (optional).

No response

Originally created by @tobiswdec on GitHub (Nov 29, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9500 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? documenso ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/documenso.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-17-pve) ### 📝 Provide a clear and concise description of the issue. Script exit with fatal error ### 🔄 Steps to reproduce the issue. default options with verbose ### ❌ Paste the full error output (if available). [...] @documenso/remix:build: created build/server/hono in 18.1s [Build]: Done in 84 seconds Tasks: 3 successful, 3 total Cached: 0 cached, 3 total Time: 1m33.936s > @documenso/root@2.1.0 prisma:migrate-deploy > npm run with:env -- npm run prisma:migrate-deploy -w @documenso/prisma > @documenso/root@2.1.0 with:env > dotenv -e .env -e .env.local -- npm run prisma:migrate-deploy -w @documenso/prisma > @documenso/prisma@0.0.0 prisma:migrate-deploy > prisma migrate deploy warn The configuration property `package.json#prisma` is deprecated and will be removed in Prisma 7. Please migrate to a Prisma config file (e.g., `prisma.config.ts`). For more information, see: https://pris.ly/prisma-config Prisma schema loaded from schema.prisma Error: Prisma schema validation - (get-config wasm) Error code: P1012 error: Environment variable not found: NEXT_PRIVATE_DIRECT_DATABASE_URL. --> schema.prisma:24 | 23 | url = env("NEXT_PRIVATE_DATABASE_URL") 24 | directUrl = env("NEXT_PRIVATE_DIRECT_DATABASE_URL") | Validation Error Count: 1 [Context: getConfig] Prisma CLI Version : 6.19.0 npm error Lifecycle script `prisma:migrate-deploy` failed with error: npm error code 1 npm error path /opt/documenso/out/packages/prisma npm error workspace @documenso/prisma@0.0.0 npm error location /opt/documenso/out/packages/prisma npm error command failed npm error command sh -c prisma migrate deploy [ERROR] in line 82: exit code 0: while executing command $STD npm run prisma:migrate-deploy ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:51:16 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:51:17 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 29, 2025):

@community-scripts/contributor lets remove it, im done with fixing every Release and never get Response by their devs

@MickLesk commented on GitHub (Nov 29, 2025): @community-scripts/contributor lets remove it, im done with fixing every Release and never get Response by their devs

kerem commented

2026-02-26 12:51:17 +03:00

Author

Owner

@Mythie commented on GitHub (Dec 1, 2025):

Looked at this since someone had brought it up to me. I'd venture a guess that the reason for needing to fix it every release is due to it not handling LXC containers well, personally when running LXC containers a few years back I constantly ran into this issue.

I looked through the current scripts for other services and saw that we could probably just use a docker container to run everything like Komodo and others do.

I've updated the script and created a private PR which would do all this and handle existing installations so they could upgrade nicely. One caveat is that it's currently missing a create user script that was present in the original.

I personally don't run Proxmox so I can't formally verify that the linked PR works as expected but based on existing patterns it should.

https://github.com/Mythie/proxmox-scripts/pull/1/

If someone wants to run with that it should just work provided we don't break our docker container which is unlikely.

@Mythie commented on GitHub (Dec 1, 2025): Looked at this since someone had brought it up to me. I'd venture a guess that the reason for needing to fix it every release is due to it not handling LXC containers well, personally when running LXC containers a few years back I constantly ran into this issue. I looked through the current scripts for other services and saw that we could probably just use a docker container to run everything like Komodo and others do. I've updated the script and created a private PR which would do all this and handle existing installations so they could upgrade nicely. One caveat is that it's currently missing a create user script that was present in the original. I personally don't run Proxmox so I can't formally verify that the linked PR works as expected but based on existing patterns it _should_. https://github.com/Mythie/proxmox-scripts/pull/1/ If someone wants to run with that it should just work provided we don't break our docker container which is unlikely.

kerem referenced this issue

2026-02-26 13:33:49 +03:00

[PR #2091] [MERGED] Revert "Add new LXC: Paperless-AI" #3532

kerem referenced this issue

2026-02-26 13:33:49 +03:00

[PR #2093] [MERGED] New Script: Paperless-AI #3534

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2091

No description provided.

Rows
Columns