78 lines
3.0 KiB
YAML
78 lines
3.0 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. Lockfile om dubbele, gelijktijdige deployments te voorkomen
|
|
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 ---"
|
|
|
|
# Fallback routine bij crashes
|
|
error_handler() {
|
|
echo "!!! DEPLOYMENT FAILED on line $1 !!!" >&2
|
|
echo "Attempting to keep the current service running..." >&2
|
|
sudo systemctl start atom-nexst.service || true
|
|
exit 1
|
|
}
|
|
trap 'error_handler $LINENO' ERR
|
|
|
|
# 2. Systeem opruimen
|
|
docker image prune -f
|
|
|
|
# 3. Git updates & Rechten
|
|
cd /var/www/atom-nexst/
|
|
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
|
|
|
|
# Schoonmaken met behoud van .env en de cruciale Next.js cache map (.next/cache)
|
|
# We sluiten expliciet de .next map uit van 'git clean' zodat de build cache overleeft
|
|
git clean -fd -e .env -e .env.local -e .env.production -e .env*.local -e .next
|
|
|
|
# Verwijder oude builds, maar BEHOUD de cache-map binnen .next
|
|
find .next -mindepth 1 -maxdepth 1 ! -name 'cache' -exec rm -rf {} + 2>/dev/null || true
|
|
|
|
# 4. Dependencies installeren met de nieuwste PNPM security flags
|
|
export PNPM_CONFIG_ONLY_BUILT_DEPENDENCIES="@parcel/watcher,@swc/core,sharp"
|
|
pnpm install --frozen-lockfile
|
|
|
|
# 5. Database & Prisma
|
|
pnpm db:migrate
|
|
pnpm prisma:generate
|
|
|
|
# 6. Next.js Build
|
|
# NEXT_DISABLE_SOURCEMAPS bespaart enorm veel RAM tijdens de build (fijn voor rustige server-resources)
|
|
export NEXT_DISABLE_SOURCEMAPS=1
|
|
pnpm build
|
|
|
|
# 7. Rechten corrigeren voor de webserver
|
|
# Zorgt dat www-data de nieuwe bestanden kan lezen, maar behoudt schrijfrechten voor de deployer
|
|
sudo chown -R www-data:www-data /var/www/atom-nexst/
|
|
sudo chmod -R g+rw /var/www/atom-nexst/
|
|
|
|
# 8. Service herstarten en controleren
|
|
echo "Hard resetting systemd service..."
|
|
sudo systemctl stop atom-nexst.service || true
|
|
pkill -f 'next-server' || true
|
|
|
|
sudo systemctl start atom-nexst.service
|
|
|
|
sleep 2
|
|
if ! systemctl is-active --quiet atom-nexst.service; then
|
|
echo "ERROR: atom-nexst.service failed to start!" >&2
|
|
exit 1
|
|
fi
|
|
|
|
echo "--- Deployment successfully completed ---" |