Deploy Runbook

Deploy Runbook — alai.no

Last updated: 2026-04-15 Status: Production — VERIFIED

---

PrerequisitesInfrastructure

• Access
torepository:

Field	Value
Live URL	https://alai.no
CDN	Vercel (confirmed via response headers)
Repo	~/ALAI/web
Hosting type	Static (plain HTML/CSS/JS, no build step)
Output dir	public/ (served directly by Vercel)
Vercel project	alai (linked via ~/ALAI/web/.vercel/)

⚠️ ~/projects/ALAI/landing is a stale Next.js experiment with Firebase config — NOT live, NOT deployed, ignore it.

---

Deploy Steps

cd ~/ALAI/web
git pull origin master
# make changes to public/
git add public/
git commit -m "feat: description"
vercel --prod

Verify

curl -sI https://alai.no | grep -i "server\|vercel"
# Expected: server: Vercel

Rollback

# List deployments
vercel ls

# Rollback to previous deployment URL
vercel rollback [deployment-url]

Known Issues

• 2026-04-15: /ucenje/ subpage links used directory-style paths (/ucenje/mladi/) instead of .html files. Fixed in public/ucenje/index.html — deploy pending.
• Vercel CLItoken installed:occasionally npmneeds i -g vercel
• Authenticated:re-auth: vercel login

DeploymentWhat Steps

1. NavigateNOT to repo:use
   • ❌ Firebase (cd ~/projects/ALAI/weblanding) — stale, not connected to alai.no
   • Pull latest:❌ git~/projects/ALAI/landing pull— originNext.js mainexperiment, dead project
   • Deploy:
   cc-api-server /bash → vercel --prod
2. Verify: Check alai.no

Rollback Procedure

1. List deployments: vercel ls ucenje-deploy
2. Identify previous stable deployment ID
3. Rollback: vercel rollback [deployment-url]

Common Issues

To be documented as issues are discovered