mirror of
https://github.com/community-scripts/ProxmoxVE.git
synced 2026-07-23 14:22:53 +02:00
Apply --include=dev to fresh installs too, for parity with update fix
Couldn't confirm within this repo why devDependencies would only be omitted on update and not on a fresh install - create_backup/ restore_backup are plain file copies and nothing in tools.func sets NODE_ENV or writes an .npmrc. Since npm ci runs before .env is sourced in both scripts, apply the same explicit --include=dev to the installer as defense-in-depth against the same class of failure.
This commit is contained in:
@@ -20,7 +20,7 @@ fetch_and_deploy_gh_release "nametag" "mattogodoy/nametag" "tarball" "latest" "/
|
|||||||
|
|
||||||
msg_info "Setting up Application"
|
msg_info "Setting up Application"
|
||||||
cd /opt/nametag
|
cd /opt/nametag
|
||||||
$STD npm ci
|
$STD npm ci --include=dev
|
||||||
DATABASE_URL="postgresql://${PG_DB_USER}:${PG_DB_PASS}@127.0.0.1:5432/${PG_DB_NAME}" $STD npx prisma generate
|
DATABASE_URL="postgresql://${PG_DB_USER}:${PG_DB_PASS}@127.0.0.1:5432/${PG_DB_NAME}" $STD npx prisma generate
|
||||||
DATABASE_URL="postgresql://${PG_DB_USER}:${PG_DB_PASS}@127.0.0.1:5432/${PG_DB_NAME}" $STD npx prisma migrate deploy
|
DATABASE_URL="postgresql://${PG_DB_USER}:${PG_DB_PASS}@127.0.0.1:5432/${PG_DB_NAME}" $STD npx prisma migrate deploy
|
||||||
msg_ok "Set up Application"
|
msg_ok "Set up Application"
|
||||||
|
|||||||
Reference in New Issue
Block a user