From 2e1c258bf49cadcaa55a5b0c64842005ac198b17 Mon Sep 17 00:00:00 2001
From: Remco <1+remco@noreply.gitlabi@epicnabbo.nl>
Date: Sun, 12 Jul 2026 14:25:13 +0200
Subject: [PATCH] Update .gitea/workflows/deploy.yaml

---
 .gitea/workflows/deploy.yaml | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/.gitea/workflows/deploy.yaml b/.gitea/workflows/deploy.yaml
index 3a27bf42..c370d363 100644
--- a/.gitea/workflows/deploy.yaml
+++ b/.gitea/workflows/deploy.yaml
@@ -18,6 +18,9 @@ jobs:
           # 2. Navigate to your website directory
           cd /var/www/atom-nexst/
           
+          # CRITICAL: Prevent Git permission blocks caused by the www-data ownership change
+          git config --global --add safe.directory /var/www/atom-nexst
+          
           # Point Git directly to the local Gitea folder path
           git remote set-url origin /docker/gitea/gitea/git/repositories/remco/epicnext-cms.git/
           
@@ -28,13 +31,11 @@ jobs:
           # REMOVE OLD CACHE AND BUILDS
           rm -rf .next .output dist
           
-          # 4. Configure trusted dependencies globally for this session and install
+          # 4. Configure trusted dependencies globally and install cleanly
           export PNPM_CONFIG_ONLY_BUILT_DEPENDENCIES="@parcel/watcher,@swc/core,sharp"
-          pnpm install --frozen-lockfile
+          pnpm install
           
-          # 5. Apply versioned CMS migrations and generate the Prisma client.
-          # Never run `prisma db pull` during deploy: it rewrites schema.prisma
-          # from the live emulator database and can discard CMS schema metadata.
+          # 5. Apply versioned CMS migrations and generate the Prisma client safely
           pnpm db:migrate
           pnpm prisma:generate
           
@@ -56,4 +57,4 @@ jobs:
             exit 1
           fi
           
-          echo "--- Deployment successfully completed ---"
+          echo "--- Deployment successfully completed ---"
\ No newline at end of file