Publish Pages

Use publish for local HTML, Markdown, and OpenAPI files.

npx @internalpage/cli login
npx @internalpage/cli publish ./report.html --slug weekly-report

The first run creates a page. Later runs with the same slug update that page and keep the viewer URL stable.

npx @internalpage/cli publish ./report.html --slug weekly-report

The CLI stores the returned page ID in .internalpage/config.json for the current project. If that local state is missing, the CLI looks for an existing page with the same slug in your workspace before creating a new page.

Supported Files

npx @internalpage/cli publish ./report.html --slug q2-report
npx @internalpage/cli publish ./runbook.md --slug incident-runbook
npx @internalpage/cli publish ./openapi.yaml --slug billing-api

Supported extensions:

• .html
• .htm
• .md
• .markdown
• .yaml
• .yml
• .json

Automation

For scripts and agents, use --json so the page ID and viewer URL are easy to parse.

npx @internalpage/cli publish ./report.html --slug weekly-report --json

For CI jobs, store the token in your CI secret manager and expose it as IP_TOKEN.

IP_TOKEN="${INTERNALPAGE_TOKEN}" \
npx @internalpage/cli publish ./openapi.yaml --slug billing-api --json

Specific Page IDs

Use --page when you already know the exact page ID and do not want the CLI to look up or create by slug.

npx @internalpage/cli publish ./report.html --page pg_xxx