name: Local Build and Deploy on: push: branches: - main jobs: deploy: runs-on: shell steps: - name: Run Deploy Scripts Locally run: | set -e # Define a lockfile to prevent double, concurrent deployments 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: If anything crashes during the steps below, # try to keep the current service running so the site doesn't stay down. 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 # 1. Clean up unused build images safely docker image prune -f # 2. Navigate to your website directory cd /var/www/atom-nexst/ DEPLOY_USER="$(id -un)" DEPLOY_GROUP="$(id -gn)" # CRITICAL: last deploy chowns the tree to www-data. Reclaim ownership # BEFORE git reset, otherwise stale sources can survive and break builds. sudo chown -R "${DEPLOY_USER}:${DEPLOY_GROUP}" /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/ # 3. Fetch and update code echo "Fetching origin/main..." git fetch origin --prune # Only touch files that actually have sticky bits (fast). Clearing # every tracked path one-by-one can hang the runner for minutes. echo "Clearing sticky git index bits (if any)..." STICKY_LIST="$(git ls-files -v | awk '/^[a-zS]/ {print substr($0,3)}' || true)" if [ -n "${STICKY_LIST}" ]; then echo "${STICKY_LIST}" | while IFS= read -r f; do [ -n "$f" ] || continue git update-index --no-skip-worktree --no-assume-unchanged -- "$f" 2>/dev/null || true done echo "Cleared sticky bits on $(echo "${STICKY_LIST}" | grep -c . || true) path(s)" else echo "No sticky bits found" fi echo "Hard reset to origin/main..." git reset --hard origin/main # Nuclear: delete src/ on disk, then restore ONLY from git objects. # Defeats host-local ghosts that survive reset when index flags pin old bytes. echo "Nuclear-replacing src/ from HEAD..." rm -rf src git checkout -f HEAD -- src # Drop other stray untracked junk under the app root (keep secrets/env). git clean -fd -e .env -e .env.local -e .env.production -e .env*.local # After sticky clear + nuclear replace, content diff is trustworthy again. if ! git diff --exit-code HEAD -- src >/dev/null; then echo "ERROR: src/ still differs from HEAD after nuclear checkout:" >&2 git diff --stat HEAD -- src >&2 || true exit 1 fi echo "Verified src/ matches HEAD" # Drop incremental TS caches that can hide real type errors. rm -f tsconfig.tsbuildinfo .tsbuildinfo find . -maxdepth 3 -name '*.tsbuildinfo' -delete 2>/dev/null || true # Clear generated Next types/dev dirs, but keep .next/cache for faster rebuilds. # Full src/ nuclear replace above already guarantees sources match HEAD. rm -rf .output dist .next/types .next/dev # Release tag for Sentry / logs (short git sha) export APP_VERSION="$(git rev-parse --short HEAD)" export NEXT_PUBLIC_APP_VERSION="${APP_VERSION}" echo "APP_VERSION=${APP_VERSION}" # 4. Install — onlyBuiltDependencies comes from pnpm-workspace.yaml # (do not set a PNPM only-built-deps env override here). pnpm install --frozen-lockfile # 5. Apply versioned CMS migrations and generate the Prisma client safely pnpm db:migrate pnpm prisma:generate # 6. Pre-deploy quality gates (fail before build if broken) pnpm typecheck pnpm test # 7. Next.js Build # Skip env refine during compile/page-data; runtime still validates via env.ts. export SKIP_ENV_VALIDATION=1 pnpm build # 8. Fix ownership: Build first, THEN set permissions for the web server sudo chown -R www-data:www-data /var/www/atom-nexst/ # 9. Hard restart of the Systemd service to clear memory cache echo "Hard resetting systemd service..." sudo systemctl stop atom-nexst.service || true # Kill any lingering next-server processes holding port 3000 pkill -f 'next-server' || true sudo systemctl start atom-nexst.service # 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 exit 1 fi echo "--- Deployment successfully completed ---"