Choose the right configuration
The CLI uses its user’s connection configuration. On a remote connection, application files come from the CLI machine; builds and containers run on the Engine machine.
Change Engine settings
Use the CLI to validate changes, preview a redacted diff, and record the update in the audit log:Apply a configuration file
nerdit config set accepts scalar key=value assignments. For nested tables or arrays, use a TOML file:
daemon-settings.toml
nerdit config apply - reads TOML from stdin. Preserve existing credentials when editing config.toml directly; do not replace the entire file with an example.
Application settings
nerdit.toml
port is the container’s listening port. Bind the application to 0.0.0.0 inside its container. The Engine allocates the host port; do not assume it equals 8000.
Use health_type = "tcp" for a TCP probe instead of an HTTP path. Choose a probe that actually reflects readiness. Every application gets persistent /data storage by default; custom named volumes must use the supported name:/container/path form.
Inspect or update a deployed application’s settings:
${secrets.API_KEY}. Never commit a real secret into nerdit.toml.
Continue with deployment, AI bindings, database bindings, or networking.