>docsplaygroundgithubdeploy

Deploy Overview

Deploy Tish apps to Zectre with zectre-cli and the Zectre Platform.

Hosted deployment in this guide means Zectre: the zectre CLI plus the Zectre Platform (API, scheduler, build service, registry, agents, proxy). The language is Tish; Lattish is a separate editor extension and does not change how you deploy.

Two ways to run on Zectre

PathWhat runsYou provide
Native Tish (default)Platform builds a Tish native binary and the agent runs itSource + zectre.yaml / package.json build config
DockerAgent pulls and runs a container imageImage in a registry + deploy.process_type: docker and deploy.image in zectre.yaml (or --image on the CLI)

See Docker on Zectre for images. For compiling Tish to WASM, JS, or binaries you run yourself, see Other hosts.

Flow (native Tish)

  1. Build — Platform (or local zectre build) compiles Tish source to a native binary.
  2. Upload — Artifact is stored; deployment references it.
  3. Run — Agents run the binary; the proxy routes HTTP(S) to it.

Docker skips the Tish compile step on the platform: you build and push the image, then deploy.

Components

ComponentRole
zectreAuth, projects, link, deploy, logs, env vars (Vercel-style workflow for this platform)
Zectre PlatformAPI, scheduler, agents, proxy, registry, build service

See Platform for architecture. Config reference: zectre.yaml.

Quick start (against a running platform)

From your app directory (with a zectre.yaml or package.json with a tish section):

zectre login
zectre projects add my-app
zectre deploy --wait

zectre projects add creates the app and links the current directory. Alternatively: zectre projects create my-app then zectre link.

In CI or other non-interactive environments, link first (zectre link or zectre projects add), and set ZECTRE_CLUSTER_ID (and optionally ZECTRE_API_URL) when multiple clusters exist — see the zectre-cli README.

Self-hosting the platform (developers)

To run the stack locally for development, clone zectre-platform and use just setup then just run-all. That is not required to deploy an app to an existing Zectre deployment.

Config files

  • zectre.yaml — Deploy spec (replicas, process_type, image, resources, networking). Build fields in YAML are used only when package.json has no tish section (see zectre.yaml).
  • .zectre/<cluster>/project.json — Written by zectre link; maps this directory to a platform app for that cluster.

Improve this documentation