Files
backend/scripts/websites-agent
Alireza HassaniandCursor 40284df880 Surface the real build error when website deploy.sh fails.
Super Admin was only showing "exited with code 1" because the ERR trap never copied the last compiler or module-not-found line from the deploy log.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-08-25 17:39:03 +03:30
..

Websites deploy / provision agent (runs on websites VM: /opt/websites-agent)

Endpoints (X-Deploy-Token):

POST /deploy { slug, wait?: true } — git pull + build + pm2 restart

wait=true (API default): sync, returns success/failed

wait=false: fire-and-forget 202 accepted

GET /deploy-status?slug=… — last deploy status JSON for slug

POST /provision { slug, host, gitRepoUrl } — clone + nginx + ecosystem + allowlist (no certbot)

POST /ssl { host, slug? } — certbot for apex + www (nginx must exist)

GET /health

Scripts on the VM (same folder):

patch-nginx-seo.sh — add /sitemap.xml + /robots.txt API proxies to an existing nginx site

Env (.env): PORT, DEPLOY_TOKEN, ALLOWED_SLUGS

Note: provision.sh intentionally skips certbot. SSL is issued via POST /ssl so

Edit/Add Domain does not hang when www DNS is wrong.

deploy.sh checks out origin/HEAD (falls back to main, then master).

If the site builds with Next output: 'standalone', deploy copies static/public

into .next/standalone, points PM2 at server.js, and removes full node_modules.