portaljs-deploy

1# PortalJS — Deploy
2 
3## Overview
4 
5Publish an existing PortalJS portal to **PortalJS Arc** — Datopian's managed static
6hosting on Cloudflare. Build a static export, upload it to the Arc API, and print a live
7`https://SLUG.arc.portaljs.com` URL. Re-running redeploys the same portal (idempotent on
8the slug). This is a single-target skill — it deploys to Arc only. For self-hosting, run
9`npm run build` and upload `out/` to any static host; no skill required for that path.
10Arc serves static exports only — SSR is not hosted on Arc yet.
11 
12## Prerequisites
13 
14- A PortalJS portal directory with a `package.json` that lists `next` as a dependency.
15- Node 18+ and npm on PATH (the Arc device-login flow uses Node's global `fetch`).
16- `curl` and `tar` available for packaging and upload.
17- A PortalJS Arc token — read from `PORTALJS_TOKEN`, or `~/.portaljs/credentials`
18  (`{"token":"…"}`). If neither exists, the skill signs in on demand via a device-code
19  flow; no manual token copying required.
20- If the portal stores large data in Git LFS/R2, do not run `git lfs pull` before
21  deploying — large datasets are served from Cloudflare R2 via absolute URLs in
22  `datasets.json`, not copied into the export.
23 
24## Instructions
25 
26The canonical, full step-by-step workflow is
27[`.claude/commands/portaljs-deploy.md`](https://github.com/datopian/portaljs/blob/main/.claude/commands/portaljs-deploy.md) — the
28single source of truth. Read and follow it when executing. Summary:
29…