Files
EpicNext-Cms/.gitea/workflows/deploy.yaml
T
remco d488162bec
Local Build and Deploy / deploy (push) Failing after 48s
Update .gitea/workflows/deploy.yaml
2026-07-18 16:03:40 +02:00

105 lines
4.3 KiB
YAML

name: Local Build and Deploy
on:
push:
branches:
- main
jobs:
deploy:
runs-on: shell
steps:
- name: Run Deploy Scripts Locally
run: |
set -e
# 1. Deployment lock & init
exec 9>/var/tmp/epic_web_control_deploy.lock
flock -n 9 || { echo "ERROR: Another deployment is already running! Cancelling."; exit 1; }
echo "--- EPIC WEB CONTROL: Starting Auto-Cleanup & Deploy ---"
error_handler() {
echo "!!! DEPLOYMENT FAILED on line $1 !!!" >&2
sudo systemctl restart atom-nexst.service || true
exit 1
}
trap 'error_handler $LINENO' ERR
# Zorg dat de permanente opslagmap buiten het project bestaat
sudo mkdir -p /var/www/atom-media
sudo chown -R www-data:www-data /var/www/atom-media
sudo chmod -R 775 /var/www/atom-media
# Red de huidige live uploads (nieuws, logo's) EERST voordat Git of de build iets wist
cd /var/www/atom-nexst/
if [ -d .next/standalone/public ]; then
echo "Backing up current live images and uploads..."
rsync -av --ignore-existing .next/standalone/public/ /var/www/atom-media/ || true
fi
# 2. Cleanup & Git Sync
docker image prune -f
git config --global --add safe.directory /var/www/atom-nexst
git remote set-url origin /docker/gitea/gitea/git/repositories/remco/epicnext-cms.git/
git fetch origin --prune
git reset --hard origin/main
# Sluit de public map uit zodat Git clean de lokale werkmap niet leegtrekt
git clean -fd -e .env -e .env.local -e .env.production -e .env*.local -e .next -e public
# Verwijder oude builds, behoud de cache voor snelheid
find .next -mindepth 1 -maxdepth 1 ! -name 'cache' -exec rm -rf {} + 2>/dev/null || true
# 3. Environment Sanitization
if [ -f .env ]; then
export $(grep -v '^#' .env | xargs)
export DATABASE_URL=$(echo "$DATABASE_URL" | sed 's/[&?]connect_timeout=[^&]*//g')
fi
# 4. Dependencies & Database
export PNPM_CONFIG_ONLY_BUILT_DEPENDENCIES="@parcel/watcher,@swc/core,sharp"
export PRISMA_SKIP_POSTINSTALL_GENERATE=1
pnpm install --frozen-lockfile
pnpm db:migrate
pnpm prisma:generate
# 5. Standalone Next.js Build
export NEXT_DISABLE_SOURCEMAPS=1
export NEXT_TELEMETRY_DISABLED=1
export UV_THREADPOOL_SIZE=2
export SKIP_ENV_VALIDATION=true
pnpm build
# 6. Sync Standalone Bundle
echo "Preparing standalone bundle paths..."
# Kopieer de schone, nieuw gebouwde public-map naar standalone
cp -r public .next/standalone/
cp -r .next/static .next/standalone/.next/
cp -r node_modules/@prisma .next/standalone/node_modules/ 2>/dev/null || true
cp .env .next/standalone/.env
# Kopieer nu alle bewaarde nieuws-images, logo's en uploads terug over de standalone public-map heen
if [ -d /var/www/atom-media ]; then
echo "Restoring all news images and uploads to production..."
rsync -av /var/www/atom-media/ .next/standalone/public/
fi
# 7. Permissions (GEBRACHT VÓÓR HET HERSTARTEN)
# We forceren de rechten NU op alle gekopieerde bestanden, inclusief de teruggezette rsync-bestanden
sudo chown -R www-data:www-data /var/www/atom-nexst/
sudo chmod -R g+rw /var/www/atom-nexst/
# 8. Restart & Check
echo "Restarting systemd service gracefully..."
sudo systemctl daemon-reload
sudo systemctl restart atom-nexst.service
# Geef Node.js 3 seconden de tijd om op te starten en de databaseverbinding te openen
sleep 3
if ! systemctl is-active --quiet atom-nexst.service; then
echo "ERROR: atom-nexst.service failed to start! Check logs using: journalctl -u atom-nexst.service" >&2
exit 1
fi
echo "--- Deployment successfully completed ---"