Update .gitea/workflows/deploy.yaml
Local Build and Deploy / deploy (push) Successful in 41s

This commit is contained in:
remco committed 2026-07-12 13:51:29 +02:00
1 parent a758cb3bfe
commit e588fc8162
1 file changed
+8 -7
+8 -7
View File
@@ -25,8 +25,8 @@ jobs:
git fetch origin --prune git fetch origin --prune
git reset --hard origin/main git reset --hard origin/main
# Optioneel: Verwijder de oude build map om caching problemen te voorkomen # VERWIJDER OUDE CACHE EN BUILDS (Pas aan naar .output, .next of dist afhankelijk van je framework)
rm -rf .next rm -rf .next .output dist
# 4. Configure pnpm to automatically approve build scripts # 4. Configure pnpm to automatically approve build scripts
pnpm config set trusted-dependencies @parcel/watcher,@swc/core,sharp pnpm config set trusted-dependencies @parcel/watcher,@swc/core,sharp
@@ -37,14 +37,15 @@ jobs:
pnpm prisma generate pnpm prisma generate
pnpm build pnpm build
# 5. Fix ownership: Eerst bouwen, DAARNA pas alle rechten naar de webserver zetten # 5. Fix ownership: Eerst bouwen onder de runner, DAARNA pas naar de webserver zetten
sudo chown -R www-data:www-data /var/www/atom-nexst/ sudo chown -R www-data:www-data /var/www/atom-nexst/
# 6. Restart the application service # 6. Harde herstart van de Systemd service
echo "Restarting service..." echo "Hard resetting systemd service..."
sudo systemctl restart atom-nexst.service sudo systemctl stop atom-nexst.service
sudo systemctl start atom-nexst.service
# Extra check: Controleer of de service echt goed draait # Extra check: Staat hij echt aan?
sleep 2 sleep 2
if ! systemctl is-active --quiet atom-nexst.service; then if ! systemctl is-active --quiet atom-nexst.service; then
echo "ERROR: atom-nexst.service failed to start!" >&2 echo "ERROR: atom-nexst.service failed to start!" >&2