Skip to main content

CLI Deployment Registration

Use the CLI for the complete deployment flow. Install it as described in Deployment Files and Directories.

sl deployment guide --json
sl deployment login --base-url https://api.solncn.com \
  --tenant '<tenant-subdomain>' --email '<member-email>'
sl deployment status --json

status shows the registration and latest release without printing an Agent secret.

Register a Server Runtime​

Run on the server that will host the containers, after preparing DNS, HTTPS, and encrypted storage:

sl deployment register --dir /opt/soln-tenant-runtime \
  --deployment-target server --deployment-mode singleMachine \
  --runtime-origin https://runtime.customer.example.com
sl deployment prepare --dir /opt/soln-tenant-runtime

Use --deployment-mode externalServices when registering external services mode. For this-computer deployments, see This-Computer Installation.

Registration saves .soln-install-setup.json with mode 0600, including the Agent secret. Do not print it, copy it to shared storage, or commit it to Git. Install with --setup-file; tenant IDs, Runtime IDs, and secrets do not need to be copied into arguments.

An existing registration is rejected by default. Use register --force only for an intentional replacement: it replaces the Agent secret and prevents the old Runtime from renewing with its old credential. Retry installation after fixing a local check failure instead of registering again. If registration succeeds but saving the setup file fails, the original secret cannot be retrieved; plan a replacement registration.

prepare checks the saved setup against the Control Plane registration. Use sl upgrade for an installed directory.

Next: Single-Machine Installation.