platform>docssolutionspricingcontact

First deployment

From a fresh machine to a running task — auth, manifest, deploy, and verify.

The story

You have a service you want on Zectre: typically a Tish build (zectre build / platform build) or a Docker image (process_type: docker + deploy.image), a zectre.yaml that describes build and networking, and a platform endpoint (self-hosted or hosted).

Steps

1. Install the CLI

See Installation.

2. Authenticate

Catalog-backed OAuth or legacy — pick one path in Authentication.

3. Add a project manifest

At minimum your manifest should name the app, declare build (or Docker image) inputs, and networking.port so the proxy can route. Start from the sample in Configuration.

4. Create / link

zectre projects add my-service

5. Deploy

zectre deploy --wait

6. Verify

zectre status

Grab a task id from the dashboard or API, then:

zectre logs <task-id> -f

Hit the preview or production URL your operator configured — host resolution on the proxy is described in Local development.

What you learned

  • CLI carries identity and link state; platform services carry scheduling, artifacts, and routing metadata.
  • Rough data path: builds land in registry (or image pull on the node); the scheduler tells agents what to run; proxy maps HTTP to the task’s {address}:{port} using DB state.

When you are ready to reason about the moving parts, read Architecture tour.