Skip to content
Nautilo Documentation
Deploy / Build / AdministerDeploy

Deploy locally

Review the in-progress release-candidate path for a claimed local Compose Server.

Use this path for one-machine evaluation or a private Server whose lifecycle belongs on the operator's workstation.

Prerequisites

  • The released Nautilo CLI and an immutable released server-image tag.
  • Docker Engine running locally.
  • A valid mode-0600 ~/.config/nautilo/deploy.toml and its referenced credentials, prepared in the quickstart.

Create the profile

nautilo profile add circle-local \
  --transport=local \
  --lifecycle=compose \
  --instance-id=circle \
  --tag=<immutable-tag> \
  --yes

The profile is non-secret connection and lifecycle metadata. The command sets it active by default.

Deploy and claim

nautilo deploy --from-registry --tag <immutable-tag>
nautilo profile current
nautilo status

deploy is the first-install path. It has no automatic backup or rollback. When deploy.toml is present and unconsumed, the release-candidate CLI applies its providers and first-owner claim during this transaction.

Prove the result

Do not stop at container health. Confirm that:

  1. nautilo profile current reports the expected profile, instance identity, and Server URL, while nautilo status reports running Compose and setup state;
  2. setup state is ready rather than fresh and unclaimed;
  3. the owner can sign in with the credentials recorded before deployment; and
  4. a configured model answers through the connected client.