Client Portal Deploy

Client portal (frontend/client/, Next.js) is deployed to Cloudflare Pages, not via the systemd deploy scripts in deploy/

Source memory file: project_client_portal_deploy.md · Category: Project / investigation This is a verbatim dump of Claude's persistent memory for the Octopus project. Rendered inside a code block so nothing is altered.

---
name: Client Portal Deploy Target
description: Client portal (frontend/client/, Next.js) is deployed to Cloudflare Pages, not via the systemd deploy scripts in deploy/
type: project
originSessionId: 4245cebe-3051-49ec-8ce6-8551f41402a3
---
The client portal in `frontend/client/` is deployed to **Cloudflare Pages**, not via systemd on the same host as the Go backend.

**Why:** User confirmed 2026-04-10 when reviewing deploy scripts — "client will be on CF pages, so ignore it."

**How to apply:**
- Don't review, edit, or suggest fixes to `deploy/setup-octopus-client-service.sh` or `deploy/update-octopus-client.sh` — they're stale/unused.
- The Go backend deploy scripts (`deploy/setup-octopus-service.sh`, `deploy/update-octopus.sh`) are still active and maintained.
- If asked to clean up unused deploy files, the client-service scripts are candidates for removal.
- Grasshopper (`frontend/grasshopper/`) is the Cloudflare Worker layer; the Next.js client app is separate and lives on CF Pages.