deploy-to-layero

Deploy to Layero

Layero is a deployment platform for static sites and SPAs with build servers and CDN located inside Russia. It ships a local directory — a git repository is not required.

Deploy

Run from the project root:

npx layero@latest deploy --json

--json switches the CLI to JSON-lines output — one JSON object per line on stdout. Parse the stream rather than scraping human-readable text.

If the directory has no .layero/project.json, run npx layero init first. It detects the framework, writes the config, and appends a rules block to AGENTS.md so later sessions follow the same procedure.

Events to handle

auth_required, authorized, project_created, project_linked, detected,
packing, uploading, uploaded, setup_applied, deploy_started, stage,
build_log, ready, error

• auth_required carries url and user_code. Render the URL as a clickable link. The user signs in once; the CLI's poll loop picks up the token within about two seconds and caches it in ~/.layero/config.json. There is no localhost callback, so the browser may be on a different machine than the terminal — this works from SSH, Docker and sandboxes.
• detected is informational: framework, build command, output directory. Do not override detection unless it is demonstrably wrong.
• build_log is raw build output. Forward it only when it contains errors.
• ready carries url — the live address. Show it as-is. Never construct the hostname from a template: addresses live in a dedicated zone, organizations migrate between zones, and a guessed host will be wrong. preview_url and edge_ready are legacy fields; do not gate on them.
• error carries a stable code and a next_action hint. Follow next_action. The codes the CLI actually emits are auth_required, auth_expired, auth_timeout, project_unknown, project_not_found, cli_deploys_disabled, invalid_type, prebuilt_no_dir, prebuilt_no_index, deploy_not_started, deploy_failed and internal. The failure code is assembled as deploy_<status> and the only failing statuses are failed and cancelled, so deploy_error and deploy_timed_out never occur.