From 3d7bd16e29b5b4315731c5d4c4c5dbf504af821a Mon Sep 17 00:00:00 2001 From: Remco <1+remco@noreply.gitlabi@epicnabbo.nl> Date: Sun, 12 Jul 2026 13:52:17 +0200 Subject: [PATCH] Update .gitea/workflows/deploy.yaml --- .gitea/workflows/deploy.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.gitea/workflows/deploy.yaml b/.gitea/workflows/deploy.yaml index 5c288d7b..12d5a4c6 100644 --- a/.gitea/workflows/deploy.yaml +++ b/.gitea/workflows/deploy.yaml @@ -25,7 +25,7 @@ jobs: git fetch origin --prune git reset --hard origin/main - # VERWIJDER OUDE CACHE EN BUILDS (Pas aan naar .output, .next of dist afhankelijk van je framework) + # REMOVE OLD CACHE AND BUILDS (Adjust to .output, .next, or dist depending on your framework) rm -rf .next .output dist # 4. Configure pnpm to automatically approve build scripts @@ -37,15 +37,15 @@ jobs: pnpm prisma generate pnpm build - # 5. Fix ownership: Eerst bouwen onder de runner, DAARNA pas naar de webserver zetten + # 5. Fix ownership: Build first, THEN set permissions for the web server sudo chown -R www-data:www-data /var/www/atom-nexst/ - # 6. Harde herstart van de Systemd service + # 6. Hard restart of the Systemd service to clear memory cache echo "Hard resetting systemd service..." sudo systemctl stop atom-nexst.service sudo systemctl start atom-nexst.service - # Extra check: Staat hij echt aan? + # Extra health check: Ensure the service is actually running sleep 2 if ! systemctl is-active --quiet atom-nexst.service; then echo "ERROR: atom-nexst.service failed to start!" >&2