`DEPLOY.md`

23 lines
# HomesOnSpec — how to deploy (sanctioned path)

**Do NOT create a generic `.deploy.conf` / use `~/Projects/_shared/scripts/deploy.sh` here.**
That script does `rsync -az --delete` over the *whole repo*. Against this project that would
sync Mac2's small `var/` over Kamatera's **~85 GB content-addressed crawl cache** (`var/snapshots`)
and delete it, and try to push the 55 GB `apps/workers/`. It is a footgun.

## The web app (the customer-facing site, homesonspec.com → Kamatera)
```
! bash ~/Projects/homesonspec/deploy-web.sh
```
This is surgical and safe: it rsyncs ONLY `apps/web/src/` → Kamatera, rebuilds
`@homesonspec/web` there, restarts `pm2 homesonspec-web`, and verifies web/map/api/https.
Never touches `var/`, data, or the workers. Verified 2026-08-06.

## Topology
- homesonspec.com → **45.61.58.125 (Kamatera)**, nginx → Next.js, `pm2 homesonspec-web`,
  repo at `/root/Projects/homesonspec`.
- The Mac2 `hos-web` pm2 process is a LOCAL mirror (its own DB) — rebuilding it does NOT
  affect the live site.
- Related deploy scripts in this repo: `deploy-web.sh` (web), `deploy-full.sh`,
  `deploy-kamatera.sh`, `golive-homesonspec.sh`. Prefer `deploy-web.sh` for web-only changes.