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.tomland 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> \
--yesThe 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 statusdeploy 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:
nautilo profile currentreports the expected profile, instance identity, and Server URL, whilenautilo statusreports running Compose and setup state;- setup state is ready rather than fresh and unclaimed;
- the owner can sign in with the credentials recorded before deployment; and
- a configured model answers through the connected client.