Skip to content

Settings Reference

The Settings page stores all application-level configuration: appearance, deployment defaults, artifact management, and policy server connectivity. Settings persist in the local SQLite database and survive application restarts.

Prerequisites

  • ntkDeploy installed and launched — see First Launch.
  • For Policy Server settings, your policy server endpoint and TLS certificates must be available.

Opening Settings

Click Settings in the left sidebar (section settings). The page loads the current values from the local database. Any change takes effect immediately — there is no save/cancel flow; each field auto-saves on change.

Appearance

Setting Options Default Notes
Theme mode System, Light, Dark System Controls whether the app follows the OS color scheme or uses a fixed theme

Deployment Defaults

These values pre-populate the Deployment Wizard when starting a new deployment.

Setting Options Default Notes
Default concurrency 5, 10, 25 5 Maximum number of parallel device deployments
Default backup strategy None, Backup, Rotate backup The pre-selected backup strategy in the wizard

Artifacts

Deployment artifacts (built JSON payloads + metadata) are stored locally for audit and rollback purposes.

Setting Type Default Notes
Retention days Slider 1–120 30 Artifacts older than this number of days are eligible for cleanup
Artifacts directory Directory picker System default Override where artifact files are written. Use the Change button to pick a directory.

Artifact Actions

Button Action
Clean up old artifacts Immediately deletes artifacts older than the configured retention period. Displays a count of deleted files.

Note: The effective artifacts directory (accounting for the default when no override is set) is displayed on the page.

Policy Server

These settings control how ntkDeploy connects to the external ntkDrive conductor and policy server for ABAC enforcement.

Setting Label Format Required for policy Notes
Conductor Address Conductor Address host:port No Default: xdrive.dev:9010. Used as the conductorAddress field in deployed configs.
Base URL Base URL https://host:port Yes Policy server HTTPS endpoint (e.g., https://policy.example.com:8443)
CA certificate path CA certificate path File path .crt, .pem, .cer Conditional TLS CA certificate for the policy server. Use the browse button to pick a file.
Client certificate path Client certificate path File path .crt, .pem, .cer Conditional TLS client certificate for mutual TLS.
Client key path Client key path File path .key, .pem Conditional Private key corresponding to the client certificate.
Signing key (hex) Signing key Hex string Conditional Masked field. Used to sign policy requests.
Public key (hex) Public key (hex, optional) Hex string No Optional public key for verification.

Testing the Connection

Click Test connection (the filled button at the bottom of the Policy Server section) to verify that ntkDeploy can reach the policy server with the configured credentials.

Result Feedback
Success Snack bar: Policy server connection succeeded.
Failure Snack bar showing the error message returned by the server or TLS layer

Note: Test connection validates endpoint reachability only — it does not directly set or unlock the Policy Connectivity Gate. Gate state is updated automatically by ntkDeploy's background connectivity monitoring based on ongoing results. See Deployment Preflight Reference for how the gate affects deployments.

Resetting Settings

There is no one-click reset to defaults. To reset individual settings:

  • Theme: change the dropdown back to System.
  • Concurrency / backup strategy: select the default values from the dropdowns.
  • Artifact retention: drag the slider back to 30 days.
  • Artifacts directory: no in-UI clear option exists. Use the Change button to select a different directory, or reset the stored path directly in the database.
  • Policy settings: clear each field individually.

Next Steps