levelrail-cli settings runtime list
levelrail-cli settings runtime get <key>
levelrail-cli settings runtime set <key> <value>
levelrail-cli settings runtime reset <key>
Security
| Key | Type | Default | Range | Env seed | Live | Description | CLI | Dashboard |
|---|---|---|---|---|---|---|---|---|
abuse.default_burst | int | 40 | value must be between 1 and 10000000 | APP_ABUSE_DEFAULT_BURST | yes | Burst size used when a policy turns rate limiting on without naming one, from 1 to 10000000. It cannot exceed the largest burst. Applies to the next policy save and the next proxy refresh. | levelrail-cli settings runtime get|set abuse.default_burst | Settings > Runtime, Security card |
abuse.default_rps | string | 20 | value must be a number between 0.1 and 1e+06 | APP_ABUSE_DEFAULT_RPS | yes | Per-client rate used when a policy turns rate limiting on without naming one, from 0.1 to 1000000. It cannot exceed the highest rate. Applies to the next policy save and the next proxy refresh. | levelrail-cli settings runtime get|set abuse.default_rps | Settings > Runtime, Security card |
abuse.dryrun_default_window | duration | 15m0s | value must be a duration between 1m0s and 24h0m0s | APP_ABUSE_DRYRUN_DEFAULT_WINDOW | yes | How long a dry run watches traffic when none is named, from 1m to 24h. It cannot exceed the longest dry run window. Applies to the next dry run. | levelrail-cli settings runtime get|set abuse.dryrun_default_window | Settings > Runtime, Security card |
abuse.dryrun_max_window | duration | 1h0m0s | value must be a duration between 1m0s and 168h0m0s | APP_ABUSE_DRYRUN_MAX_WINDOW | yes | Longest window a dry run may watch traffic, from 1m to 168h. Applies to the next dry run. | levelrail-cli settings runtime get|set abuse.dryrun_max_window | Settings > Runtime, Security card |
abuse.dryrun_top_clients | int | 10 | value must be between 1 and 100 | APP_ABUSE_DRYRUN_TOP_CLIENTS | yes | How many of the busiest clients a dry run report lists, from 1 to 100. Applies to the next dry run. | levelrail-cli settings runtime get|set abuse.dryrun_top_clients | Settings > Runtime, Security card |
abuse.idle_evict | duration | 5m0s | value must be a duration between 10s and 24h0m0s | APP_ABUSE_IDLE_EVICT | no, restart | How long a client can stay quiet before the limiter forgets it, from 10s to 24h. Set when the proxy starts, so a change needs a restart. | levelrail-cli settings runtime get|set abuse.idle_evict | Settings > Runtime, Security card |
abuse.max_agent_entries | int | 64 | value must be between 1 and 1000 | APP_ABUSE_MAX_AGENT_ENTRIES | yes | Most user agent rules one app’s abuse policy may hold, from 1 to 1000. Applies to the next policy save. | levelrail-cli settings runtime get|set abuse.max_agent_entries | Settings > Runtime, Security card |
abuse.max_burst | int | 100000 | value must be between 1 and 10000000 | APP_ABUSE_MAX_BURST | yes | Ceiling for the burst size any app’s abuse policy may set, from 1 to 10000000 requests. Applies to the next policy save and the next proxy refresh. | levelrail-cli settings runtime get|set abuse.max_burst | Settings > Runtime, Security card |
abuse.max_deny_entries | int | 256 | value must be between 1 and 10000 | APP_ABUSE_MAX_DENY_ENTRIES | yes | Most address or network entries one app’s deny list may hold, from 1 to 10000. Applies to the next policy save. | levelrail-cli settings runtime get|set abuse.max_deny_entries | Settings > Runtime, Security card |
abuse.max_retry_after | duration | 1m0s | value must be a duration between 1s and 1h0m0s | APP_ABUSE_MAX_RETRY_AFTER | yes | Upper bound on the Retry-After value sent with a rate limit rejection, from 1s to 1h. Applies at the next proxy refresh. | levelrail-cli settings runtime get|set abuse.max_retry_after | Settings > Runtime, Security card |
abuse.max_rps | string | 10000 | value must be a number between 1 and 1e+06 | APP_ABUSE_MAX_RPS | yes | Ceiling for the per-client rate any app’s abuse policy may set, from 1 to 1000000 requests per second. A policy above it is rejected when saved. Applies to the next policy save and the next proxy refresh. | levelrail-cli settings runtime get|set abuse.max_rps | Settings > Runtime, Security card |
abuse.max_tracked_clients | int | 100000 | value must be between 1000 and 10000000 | APP_ABUSE_MAX_TRACKED_CLIENTS | no, restart | How many distinct client addresses each app’s limiter remembers at once, from 1000 to 10000000. The table is sized when the proxy starts, so a change needs a restart. | levelrail-cli settings runtime get|set abuse.max_tracked_clients | Settings > Runtime, Security card |
abuse.shards | int | 64 | value must be between 1 and 1024 | APP_ABUSE_SHARDS | no, restart | How many lock shards each app’s limiter splits its client table into, from 1 to 1024. More shards cut contention on busy apps. Set when the proxy starts, so a change needs a restart. | levelrail-cli settings runtime get|set abuse.shards | Settings > Runtime, Security card |
abuse.suggest_burst_seconds | string | 2 | value must be a number between 0.1 and 60 | APP_ABUSE_SUGGEST_BURST_SECONDS | yes | The suggested burst is this many seconds of the suggested rate, from 0.1 to 60. Applies to the next suggestion. | levelrail-cli settings runtime get|set abuse.suggest_burst_seconds | Settings > Runtime, Security card |
abuse.suggest_client_share | string | 0.25 | value must be a number between 0.01 and 1 | APP_ABUSE_SUGGEST_CLIENT_SHARE | yes | Fraction of an app’s peak request rate that one client may use before the suggested limit applies, from 0.01 to 1. Applies to the next suggestion. | levelrail-cli settings runtime get|set abuse.suggest_client_share | Settings > Runtime, Security card |
api.rate_limit_read_rpm | int | 600 | value must be between 60 and 10000000 | APP_API_RATE_LIMIT_READ_RPM | yes | Read requests per minute allowed for each API token, signed-in user or client address. Requests over the budget get HTTP 429 with a Retry-After header. Minimum 60 so the dashboard keeps working; a change applies at once and keeps each caller’s current budget. A limit cannot be switched off: an environment value of 0 or below the minimum is raised to the minimum (older releases treated 0 as off). Weakening it asks for confirmation. | levelrail-cli settings runtime get|set api.rate_limit_read_rpm | Settings > Runtime, Security card |
api.rate_limit_redeem_rpm | int | 10 | value must be between 3 and 10000000 | APP_API_RATE_LIMIT_TOKEN_REDEEM_RPM | yes | Password reset and invite accept requests per minute allowed from one client address. Requests over the budget get HTTP 429. Minimum 3; a change applies at once. A limit cannot be switched off: an environment value of 0 or below the minimum is raised to the minimum (older releases treated 0 as off). Weakening it asks for confirmation. | levelrail-cli settings runtime get|set api.rate_limit_redeem_rpm | Settings > Runtime, Security card |
api.rate_limit_write_rpm | int | 120 | value must be between 20 and 10000000 | APP_API_RATE_LIMIT_WRITE_RPM | yes | Write and deploy requests per minute allowed for each API token, signed-in user or client address. Requests over the budget get HTTP 429 with a Retry-After header. Minimum 20 so an operator cannot lock themselves out; a change applies at once. A limit cannot be switched off: an environment value of 0 or below the minimum is raised to the minimum (older releases treated 0 as off). Weakening it asks for confirmation. | levelrail-cli settings runtime get|set api.rate_limit_write_rpm | Settings > Runtime, Security card |
audit.anchor_webhook_secret | string | empty | any valid string | APP_AUDIT_ANCHOR_WEBHOOK_SECRET | yes | Shared secret used to HMAC-SHA256 sign each export body, sent as X-Levelrail-Signature. Empty sends the export unsigned. | levelrail-cli settings runtime get|set audit.anchor_webhook_secret | Settings > Runtime, Security card |
audit.anchor_webhook_url | string | empty | any valid string | APP_AUDIT_ANCHOR_WEBHOOK_URL | yes | HTTPS endpoint that receives each new signed audit checkpoint (sequence, hash, signature, timestamp, never log bodies). Empty turns the export off. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set audit.anchor_webhook_url | Settings > Runtime, Security card |
auth.engine_rate_limit_per_email | int | 60 | value must be between 10 and 100000 | APP_AUTH_ENGINE_RATE_LIMIT_PER_EMAIL | no, restart | Credential requests per minute allowed for one account name from any address before it gets HTTP 429. This slows targeted password guessing; it cannot be turned off and the minimum is 10 so the owner can still sign in. An environment value below 10 is raised to 10. Needs a restart because the auth library holds the budget. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set auth.engine_rate_limit_per_email | Settings > Runtime, Security card |
auth.engine_rate_limit_per_ip | int | 60 | value must be between 10 and 100000 | APP_AUTH_ENGINE_RATE_LIMIT_PER_IP | no, restart | Credential requests (sign in, password reset, MFA) per minute allowed from one client address before it gets HTTP 429. This slows credential stuffing; it cannot be turned off and the minimum is 10 so an admin can still sign in. An environment value below 10 is raised to 10. Needs a restart because the auth library holds the budget. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set auth.engine_rate_limit_per_ip | Settings > Runtime, Security card |
auth.password_min_length | int | 8 | value must be between 8 and 128 | none | yes | Fewest characters a new password may have, from 8 to 128. Applies to sign-up, invites, password reset and password change. Existing passwords keep working until they are changed. | levelrail-cli settings runtime get|set auth.password_min_length | Settings > Runtime, Security card |
auth.password_require_classes | int | 0 | value must be between 0 and 4 | none | yes | How many of the four character types (lowercase, uppercase, digit, symbol) a new password must mix, from 0 to 4. 0 asks for no mix. Applies to sign-up, invites, password reset and password change. | levelrail-cli settings runtime get|set auth.password_require_classes | Settings > Runtime, Security card |
auth.sso_auto_redirect | bool | false | any valid bool | none | yes | When exactly one single sign-on provider is enabled, the sign-in page goes straight to it. Open the sign-in page with ?password=1 to use the password form instead, so a broken provider can never lock admins out. Off by default. | levelrail-cli settings runtime get|set auth.sso_auto_redirect | Settings > Runtime, Security card |
desktop.session_ttl | duration | 12h | any valid duration | APP_DESKTOP_SESSION_TTL | yes | How long a dashboard session issued to the desktop app stays valid before it must exchange its token again. | levelrail-cli settings runtime get|set desktop.session_ttl | Settings > Runtime, Security card |
firewall.confirm_window | duration | 60s | value must be a duration between 10s and 10m0s | APP_FIREWALL_CONFIRM_WINDOW | yes | How long a port restriction applied from the dashboard or CLI stays before it is rolled back unless someone confirms it, from 10s to 10m. The next restriction uses a changed value. | levelrail-cli settings runtime get|set firewall.confirm_window | Settings > Runtime, Security card |
fixit.max_per_hour | int | 0 | value must be between 0 and 1000 | APP_FIXIT_MAX_PER_HOUR | no, restart | Most times one fix may be applied per hour. 0 keeps the built-in cap. Read when the fix engine starts, so a change needs a restart. | levelrail-cli settings runtime get|set fixit.max_per_hour | Settings > Runtime, Security card |
git.lfs_hosts | string_list | empty | colon separated list | APP_GIT_LFS_HOSTS | yes | LFS objects download only from the repository’s own host. List the storage hosts your git server redirects LFS downloads to (for example a CDN host). The app’s credentials are never sent to them. Empty by default. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set git.lfs_hosts | Settings > Runtime, Security card |
git.ssh_scan_allow_internal | string_list | empty | colon separated list | APP_GIT_SSH_SCAN_ALLOW_INTERNAL | yes | Trust-on-first-use host key scans refuse loopback, private and link-local addresses. List the IPs or CIDR ranges of a self-hosted git server here to allow them. Cloud metadata addresses are never allowed. Empty by default. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set git.ssh_scan_allow_internal | Settings > Runtime, Security card |
git.submodules_allowed_cidrs | string_list | empty | colon separated list | APP_GIT_SUBMODULES_ALLOWED_CIDRS | yes | Submodule and LFS fetches refuse loopback, private, link-local, CGNAT, multicast and unspecified addresses, checked at connect time. List the IPs or CIDR ranges of a self-hosted git server here to allow them. Empty by default. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set git.submodules_allowed_cidrs | Settings > Runtime, Security card |
git.submodules_credential_hosts | string_list | empty | colon separated list | APP_GIT_SUBMODULES_CREDENTIAL_HOSTS | yes | A submodule on the parent repository’s host is fetched with the app’s git credentials; one on any other host is fetched without them. List extra hosts here to send the credentials there too. Empty by default. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set git.submodules_credential_hosts | Settings > Runtime, Security card |
mcp.default_token_scope | string | read_only | one of read_only, read_write | APP_MCP_DEFAULT_TOKEN_SCOPE | yes | Scope given to a new API token or MCP client token created without explicit abilities: read_only (view only) or read_write (also change config). A token can still be created with explicit abilities. Existing tokens keep their scope. The environment variable only seeds the default. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set mcp.default_token_scope | Settings > Runtime, Security card |
nodes.patch_adopt_limit | int | 20 | value must be between 1 and 200 | APP_NODES_PATCH_ADOPT_LIMIT | yes | How many package upgrade units left by a previous control plane process are picked up again, with their result recorded and audited. A unit still running keeps the node locked until it ends. | levelrail-cli settings runtime get|set nodes.patch_adopt_limit | Settings > Runtime, Security card |
nodes.patch_apply_timeout | duration | 30m | value must be a duration between 1m0s and 4h0m0s | APP_NODES_PATCH_APPLY_TIMEOUT | yes | How long the control plane waits for one package upgrade. On timeout the upgrade is left running and the run is recorded as timed_out; it is never killed. | levelrail-cli settings runtime get|set nodes.patch_apply_timeout | Settings > Runtime, Security card |
nodes.patch_preview_ttl | duration | 10m | value must be a duration between 1m0s and 1h0m0s | APP_NODES_PATCH_PREVIEW_TTL | yes | How long a patch preview stays valid. An apply must quote a preview younger than this, and the package list must still match it. | levelrail-cli settings runtime get|set nodes.patch_preview_ttl | Settings > Runtime, Security card |
nodes.protected_taint_keys | string_list | empty | colon separated list | APP_NODES_PROTECTED_TAINT_KEYS | yes | Taint keys that keep workloads off sensitive nodes. Removing one of these taints, changing its value or loosening its effect counts as weakening, which a stack token can never do; only a human root changes them. Empty protects nothing. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set nodes.protected_taint_keys | Settings > Runtime, Security card |
orgs.admins_can_create | bool | false | any valid bool | none | yes | Under strict organization isolation, also let users and tokens with the write ability create organizations. Off means only root can. It has no effect while strict isolation is off, where write is enough already. | levelrail-cli settings runtime get|set orgs.admins_can_create | Settings > Runtime, Security card |
orgs.avatar_max_bytes | int | 262144 | value must be between 16384 and 2097152 | APP_ORGS_AVATAR_MAX_BYTES | yes | Most bytes an organization avatar upload may have, from 16384 to 2097152. The next upload uses a changed value. | levelrail-cli settings runtime get|set orgs.avatar_max_bytes | Settings > Runtime, Security card |
orgs.avatar_max_dimension | int | 1024 | value must be between 64 and 4096 | APP_ORGS_AVATAR_MAX_DIMENSION | yes | Widest or tallest an organization avatar may be, from 64 to 4096 pixels. Checked from the image header before any pixels are decoded. | levelrail-cli settings runtime get|set orgs.avatar_max_dimension | Settings > Runtime, Security card |
orgs.provisioned_default_membership | bool | true | any valid bool | none | yes | New users created by single sign-on or directory sync join the default organization, which gives instance wide access. Under strict organization isolation, turn this off so they only get the organizations their group mappings grant. | levelrail-cli settings runtime get|set orgs.provisioned_default_membership | Settings > Runtime, Security card |
orgs.strict_isolation | bool | false | any valid bool | APP_ORGS_STRICT_ISOLATION | yes | Keeps every organization separate from the others. API tokens with no owner and no organization limit are treated as members of the default organization instead of instance admins, and creating an organization needs an instance admin with the root ability. Turn it on once each token is owned by a user or limited to an organization. Turning it off again loosens these checks and asks for confirmation. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set orgs.strict_isolation | Settings > Runtime, Security card |
secrets.provider_cache_ttl_seconds | int | 60 | value must be between 0 and 3600 | APP_SECRET_PROVIDER_CACHE_TTL_SECONDS | yes | Seconds a value read from Doppler, Infisical or 1Password is kept in memory and reused, from 0 to 3600. 0 reads the provider on every container start. Values are never written to disk. | levelrail-cli settings runtime get|set secrets.provider_cache_ttl_seconds | Settings > Runtime, Security card |
secrets.provider_max_response_kib | int | 1024 | value must be between 16 and 16384 | APP_SECRET_PROVIDER_MAX_RESPONSE_KIB | yes | Largest provider response read, in KiB, from 16 to 16384. A larger response fails the read instead of being parsed. | levelrail-cli settings runtime get|set secrets.provider_max_response_kib | Settings > Runtime, Security card |
secrets.provider_max_rps | int | 20 | value must be between 1 and 1000 | APP_SECRET_PROVIDER_MAX_RPS | yes | Most requests per second sent to one Doppler, Infisical or 1Password connection, from 1 to 1000. A read over the limit fails with a rate limit reason instead of waiting. The next read uses a changed value. | levelrail-cli settings runtime get|set secrets.provider_max_rps | Settings > Runtime, Security card |
secrets.provider_timeout_seconds | int | 10 | value must be between 1 and 120 | APP_SECRET_PROVIDER_TIMEOUT_SECONDS | yes | Seconds one read from Doppler, Infisical or 1Password may take, from 1 to 120. A read that runs longer fails the deploy with a timeout reason. The next read uses a changed value. | levelrail-cli settings runtime get|set secrets.provider_timeout_seconds | Settings > Runtime, Security card |
security.audit_sensitive_reads | bool | true | any valid bool | APP_AUDIT_SENSITIVE_READS | yes | Record an audit entry when logs, env exports and other sensitive data are read. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set security.audit_sensitive_reads | Settings > Runtime, Security card |
security.bind_allowed_roots | string_list | empty | colon separated list | APP_BIND_ALLOWED_ROOTS | yes | When not empty, bind mounts must sit inside one of these directories. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set security.bind_allowed_roots | Settings > Runtime, Security card |
security.bind_block_credential_dirs | bool | true | any valid bool | APP_BIND_BLOCK_CREDENTIAL_DIRS | yes | Refuse bind mounts of .ssh, .aws, .kube and similar credential directories. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set security.bind_block_credential_dirs | Settings > Runtime, Security card |
security.build_network | string | open | one of open, none, block-private | APP_BUILD_NETWORK | yes | Network for RUN steps of a build: open (no restriction), none, or block-private (reserved: builds fail until it can be enforced). Read on every build; the environment variable only seeds the default. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set security.build_network | Settings > Runtime, Security card |
security.docker_guard_max_items | int | 5 | value must be between 1 and 50 | none | yes | Most per-rule Docker guard findings the issue list shows at once, from 1 to 50. Each high-risk rule is its own item so it can be handled on its own; rules beyond the limit are counted in the last item. | levelrail-cli settings runtime get|set security.docker_guard_max_items | Settings > Runtime, Security card |
security.protected_silence_max_days | int | 30 | value must be between 0 and 3650 | none | yes | Most days a root admin may silence a security-integrity issue such as the Docker guard, from 0 to 3650. 0 allows silencing forever. The limit also applies to existing silences of these issues when they are read, counted from when each was created. | levelrail-cli settings runtime get|set security.protected_silence_max_days | Settings > Runtime, Security card |
security.webhook_replay_protection | bool | true | any valid bool | APP_WEBHOOK_REPLAY_PROTECTION | yes | Ignore a signed git webhook body that was already delivered within the replay window. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set security.webhook_replay_protection | Settings > Runtime, Security card |
security.webhook_replay_window | duration | 10m | any valid duration | APP_WEBHOOK_REPLAY_WINDOW | yes | How long an identical signed webhook body is remembered. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set security.webhook_replay_window | Settings > Runtime, Security card |
stacks.prune_max_count | int | 10 | value must be between 0 and 100000 | APP_STACK_PRUNE_MAX_COUNT | yes | A prune removing more items than this needs allow_mass_prune. From 0 to 100000; 0 means every prune needs the flag. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set stacks.prune_max_count | Settings > Runtime, Security card |
stacks.prune_max_percent | int | 50 | value must be between 0 and 100 | APP_STACK_PRUNE_MAX_PERCENT | yes | A prune removing more than this percent of a stack needs allow_mass_prune. From 0 to 100; 0 means every prune needs the flag. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set stacks.prune_max_percent | Settings > Runtime, Security card |
supply_chain.default_enabled | bool | false | any valid bool | APP_SCAN_DEFAULT_ENABLED | yes | Whether apps without their own scan policy get their images scanned. An app’s own policy always wins. Read on every deploy; the environment variable only seeds the default. | levelrail-cli settings runtime get|set supply_chain.default_enabled | Settings > Runtime, Security card |
supply_chain.default_gate | string | off | one of off, warn, block_on_critical, block_on_high | APP_SCAN_DEFAULT_GATE | yes | What a scan result does to a release for apps without their own policy: off, warn, block on critical findings or block on high findings. Needs scanning turned on to take effect. | levelrail-cli settings runtime get|set supply_chain.default_gate | Settings > Runtime, Security card |
tokens.default_ttl_days | int | 0 | value must be between 0 and 3650 | none | yes | Days a new API token lasts when the request names no expiry, from 1 to 3650. 0 keeps the built-in default of 90 days. An explicit expiry, or no expiry from a root caller, always wins, and the security policy ceiling still applies. Existing tokens are untouched. | levelrail-cli settings runtime get|set tokens.default_ttl_days | Settings > Runtime, Security card |
tokens.expiry_warning_days | int | 7 | value must be between 1 and 90 | APP_ATTENTION_TOKEN_WINDOW | yes | Days before a token you created expires that it appears as one grouped row on Status, from 1 to 90. It also bounds how long an expired token stays listed and what counts as still in use. Platform-owned tokens never show. | levelrail-cli settings runtime get|set tokens.expiry_warning_days | Settings > Runtime, Security card |
tokens.system_rotation_lead_minutes | int | 30 | value must be between 10 and 1440 | none | yes | Minutes before a platform-owned token (such as the stack drift read token) expires that the platform replaces it and revokes the old one itself, from 10 to 1440, and never less than an eighth of the token lifetime. Tokens you created are never rotated automatically. | levelrail-cli settings runtime get|set tokens.system_rotation_lead_minutes | Settings > Runtime, Security card |
tokens.unused_alert_days | int | 0 | value must be between 0 and 3650 | none | yes | Days without use after which a token is listed as unused in the token list, the doctor and the Security Center, from 1 to 3650. 0 turns the alert off. It only warns, no token is revoked. | levelrail-cli settings runtime get|set tokens.unused_alert_days | Settings > Runtime, Security card |
Networking
| Key | Type | Default | Range | Env seed | Live | Description | CLI | Dashboard |
|---|---|---|---|---|---|---|---|---|
api.conditional_get | bool | true | any valid bool | APP_API_CONDITIONAL_GET | yes | Send an ETag on read JSON responses and answer a matching If-None-Match with 304 and no body. Secret-bearing routes never get an ETag. The next request uses a changed value. | levelrail-cli settings runtime get|set api.conditional_get | Settings > Runtime, Networking card |
api.conditional_get_max_bytes | int | 4194304 | value must be between 1024 and 1073741824 | APP_API_CONDITIONAL_GET_MAX_BYTES | yes | Largest read JSON body in bytes that still gets an ETag. Bigger responses stream without one. The next request uses a changed value. | levelrail-cli settings runtime get|set api.conditional_get_max_bytes | Settings > Runtime, Networking card |
api.max_body_bytes | int | 16777216 | value must be between 1048576 and 1073741824 | APP_API_MAX_BODY_BYTES | yes | Largest JSON request body in bytes the API reads before any handler runs; a bigger body is cut off and the request fails with HTTP 413. Source uploads, git pushes and asset uploads have their own limits. Between 1 MiB and 1 GiB; a change applies to the next request. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set api.max_body_bytes | Settings > Runtime, Networking card |
apps.bundle_import_max_bytes | int | 4194304 | value must be between 4096 and 33554432 | APP_BUNDLE_IMPORT_MAX_BYTES | yes | Largest app bundle in bytes that an import accepts, from 4096 to 33554432. A bigger upload is refused. A change applies to the next import. | levelrail-cli settings runtime get|set apps.bundle_import_max_bytes | Settings > Runtime, Networking card |
apps.bundle_import_max_entries | int | 16 | value must be between 1 and 64 | APP_BUNDLE_IMPORT_MAX_ENTRIES | yes | Most files one app bundle may hold, from 1 to 64. A bundle with more entries is refused. A change applies to the next import. | levelrail-cli settings runtime get|set apps.bundle_import_max_entries | Settings > Runtime, Networking card |
apps.bundle_import_max_entry_bytes | int | 1048576 | value must be between 1024 and 8388608 | APP_BUNDLE_IMPORT_MAX_ENTRY_BYTES | yes | Largest single file in bytes inside an app bundle, from 1024 to 8388608. A bundle with a bigger file is refused. A change applies to the next import. | levelrail-cli settings runtime get|set apps.bundle_import_max_entry_bytes | Settings > Runtime, Networking card |
assets.upload_max_bytes | int | 1073741824 | value must be between 1048576 and 1099511627776 | APP_ASSETS_UPLOAD_MAX_BYTES | yes | Largest single asset object in bytes accepted by a direct or presigned upload; a bigger upload is refused with HTTP 413. Between 1 MiB and 1 TiB; direct uploads are exempt from the API request body limit and obey only this one. A change applies to the next upload. | levelrail-cli settings runtime get|set assets.upload_max_bytes | Settings > Runtime, Networking card |
certificates.weekly_issue_warn | int | 40 | value must be between 1 and 100000 | none | yes | Certificates this server received from the public CA in the last 7 days at which the certificate budget meter and the doctor show a warning, from 1 to 100000. It only warns, nothing is blocked. The next check uses a changed value. | levelrail-cli settings runtime get|set certificates.weekly_issue_warn | Settings > Runtime, Networking card |
cutover.verify_cert_fail_days | int | 7 | value must be between 1 and 365 | APP_CUTOVER_VERIFY_CERT_FAIL_DAYS | yes | Days left on a domain’s certificate at or below which the cutover verifier fails the certificate line, from 1 to 365. The next check uses a changed value. | levelrail-cli settings runtime get|set cutover.verify_cert_fail_days | Settings > Runtime, Networking card |
cutover.verify_cert_warn_days | int | 21 | value must be between 1 and 365 | APP_CUTOVER_VERIFY_CERT_WARN_DAYS | yes | Days left on a domain’s certificate at or below which the cutover verifier shows a warning, from 1 to 365. It should be at least the failure threshold; if it is lower, the failure threshold is used. The next check uses a changed value. | levelrail-cli settings runtime get|set cutover.verify_cert_warn_days | Settings > Runtime, Networking card |
cutover.verify_hsts_min_age | int | 15552000 | value must be between 3600 and 63072000 | APP_CUTOVER_VERIFY_HSTS_MIN_AGE_SECONDS | yes | Smallest HSTS max-age in seconds that the cutover verifier counts as enabled, from 3600 to 63072000 (two years). The next check uses a changed value. | levelrail-cli settings runtime get|set cutover.verify_hsts_min_age | Settings > Runtime, Networking card |
cutover.verify_min_interval | duration | 10s | value must be a duration between 1s and 1h0m0s | APP_CUTOVER_VERIFY_MIN_INTERVAL | yes | Shortest wait before the same person can run the cutover verifier again on the same domain, from 1s to 1h. Other people can check that domain after a quarter of this wait. The next check uses a changed value. | levelrail-cli settings runtime get|set cutover.verify_min_interval | Settings > Runtime, Networking card |
cutover.verify_slow_ttfb | duration | 1500ms | value must be a duration between 100ms and 30s | APP_CUTOVER_VERIFY_SLOW_TTFB | yes | Time to first byte above which the cutover verifier warns about the response, from 100ms to 30s. The next check uses a changed value. | levelrail-cli settings runtime get|set cutover.verify_slow_ttfb | Settings > Runtime, Networking card |
cutover.verify_timeout | duration | 5s | value must be a duration between 1s and 1m0s | APP_CUTOVER_VERIFY_REQUEST_TIMEOUT | yes | How long each request of the cutover verifier may take, from 1s to 1m. The whole check is allowed four times this long. It is separate from the wait after a scheduled cutover. The next check uses a changed value. | levelrail-cli settings runtime get|set cutover.verify_timeout | Settings > Runtime, Networking card |
databases.import_max_bytes | int | 1073741824 | value must be between 1048576 and 1099511627776 | APP_DATABASE_IMPORT_MAX_BYTES | yes | Largest dump in bytes accepted by a database import (databases import, POST /api/v1/databases//import); a bigger upload is refused with HTTP 413 and nothing is restored. Between 1 MiB and 1 TiB; imports are exempt from the API request body limit and obey only this one. A change applies to the next import. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set databases.import_max_bytes | Settings > Runtime, Networking card |
dns.verify_provider_on_save | bool | true | any valid bool | APP_DNS_VERIFY_PROVIDER_ON_SAVE | yes | When a DNS provider token or key is saved, also list its zones with read-only calls and report which permissions are missing. The credential is saved either way and never shown. The next save uses a changed value. | levelrail-cli settings runtime get|set dns.verify_provider_on_save | Settings > Runtime, Networking card |
doctor.reachability_dialback_allow_private | bool | false | any valid bool | none | yes | Lets the reachability dial-back URL resolve to a private or loopback address. Off by default so the check cannot be pointed at internal services. Only turn it on for a dial-back service you run on your own network. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set doctor.reachability_dialback_allow_private | Settings > Runtime, Networking card |
doctor.reachability_dialback_url | string | empty | must be an https URL | none | yes | HTTPS URL of a service that dials this server back from the internet. When set, the reachability check POSTs the list of listening ports as JSON to it, and the service learns this server’s public IP from the connection. Empty (the default) means nothing is ever contacted. The service answers with reachable and unreachable port lists. | levelrail-cli settings runtime get|set doctor.reachability_dialback_url | Settings > Runtime, Networking card |
domains.auth_gate_timeout | duration | 5s | value must be a duration between 1s and 1m0s | APP_AUTH_GATE_TIMEOUT | yes | How long the ingress waits for an auth gate’s check before it denies the request, from 1s to 1m. A domain’s own timeout wins. Applies at the next ingress refresh. | levelrail-cli settings runtime get|set domains.auth_gate_timeout | Settings > Runtime, Networking card |
domains.batch_max_items | int | 50 | value must be between 1 and 500 | APP_DOMAINS_BATCH_MAX_ITEMS | yes | Most domains one bulk park, move, attach or delete request may carry, from 1 to 500. Larger requests are rejected before any item runs. The next request uses a changed value. | levelrail-cli settings runtime get|set domains.batch_max_items | Settings > Runtime, Networking card |
domains.canonical | string | apex | must be one of [apex www] | APP_DOMAINS_CANONICAL | yes | Which host visitors end on when both are served: apex or www. The other host answers with a 308 redirect. The next plan uses a changed value. | levelrail-cli settings runtime get|set domains.canonical | Settings > Runtime, Networking card |
domains.dns_wait_budget | duration | 10m | any valid duration | APP_DOMAINS_DNS_WAIT_BUDGET | yes | How long a domain may wait for DNS before the Domains page stops saying it is fine and lists concrete checks. It only changes the wording; it never blocks onboarding. | levelrail-cli settings runtime get|set domains.dns_wait_budget | Settings > Runtime, Networking card |
domains.dns_watch_interval_seconds | int | 15 | value must be between 5 and 300 | APP_DOMAINS_DNS_WATCH_INTERVAL_SECONDS | yes | Seconds between background DNS checks of a domain that is not live yet, from 5 to 300. Checks back off while the domain keeps waiting. The next check uses a changed value. | levelrail-cli settings runtime get|set domains.dns_watch_interval_seconds | Settings > Runtime, Networking card |
domains.dns_watch_max_minutes | int | 120 | value must be between 5 and 1440 | APP_DOMAINS_DNS_WATCH_MAX_MINUTES | yes | Minutes the watcher keeps checking a domain at the normal pace, from 5 to 1440. After that the domain shows as stalled and is checked hourly for a day, then no more. | levelrail-cli settings runtime get|set domains.dns_watch_max_minutes | Settings > Runtime, Networking card |
domains.https_attempts_per_hour | int | 5 | value must be between 1 and 100 | APP_ACME_MAX_ATTEMPTS_PER_HOUR | yes | Most production certificate enable attempts allowed per hour, from 1 to 100. Guards the CA’s failed-validation limit; staging is never capped. The next attempt uses a changed value. | levelrail-cli settings runtime get|set domains.https_attempts_per_hour | Settings > Runtime, Networking card |
domains.limits_max_body_bytes | int | 1073741824 | value must be between 1048576 and 1099511627776 | APP_DOMAIN_LIMITS_MAX_BODY_BYTES | yes | Highest request body cap in bytes that a domain may set for itself, from 1 MiB to 1 TiB; the default matches the instance body limit. A domain’s own cap (domains limits set —max-body) must be at least 1 MiB and no higher than this. Caps already stored are not rewritten. The next save uses a changed value. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set domains.limits_max_body_bytes | Settings > Runtime, Networking card |
domains.limits_max_timeout_seconds | int | 3600 | value must be between 1 and 86400 | APP_DOMAIN_LIMITS_MAX_TIMEOUT_SECONDS | yes | Longest upstream read or write timeout in seconds that a domain may set for itself, from 1 to 86400. A domain’s timeout of 0 keeps the default behavior. The next save uses a changed value. | levelrail-cli settings runtime get|set domains.limits_max_timeout_seconds | Settings > Runtime, Networking card |
domains.parked_retention_days | int | 0 | value must be between 0 and 3650 | APP_DOMAINS_PARKED_RETENTION_DAYS | yes | Days a domain may stay parked before its parked registration is deleted automatically, from 0 to 3650. 0 never deletes. DNS records and certificates are never touched. Review the dry run on the Domains page before turning this on. | levelrail-cli settings runtime get|set domains.parked_retention_days | Settings > Runtime, Networking card |
domains.rollback_window_minutes | int | 60 | value must be between 1 and 10080 | APP_DOMAINS_ROLLBACK_WINDOW_MINUTES | yes | How long after a domain change (go-live or apex and www apply) it can still be rolled back, from 1 to 10080 minutes. A shorter window makes a later rollback less likely to undo someone’s newer work. The next request uses a changed value. | levelrail-cli settings runtime get|set domains.rollback_window_minutes | Settings > Runtime, Networking card |
domains.tuning_max_stream_seconds | int | 86400 | value must be between 60 and 604800 | APP_DOMAIN_TUNING_MAX_STREAM_SECONDS | yes | Longest websocket or streaming connection lifetime in seconds that a domain may set, from 60 to 604800, so no tenant can pin a connection forever. A lowered value also tightens tuning already stored on the next ingress pass. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set domains.tuning_max_stream_seconds | Settings > Runtime, Networking card |
domains.tuning_max_timeout_seconds | int | 600 | value must be between 60 and 86400 | APP_DOMAIN_TUNING_MAX_TIMEOUT_SECONDS | yes | Longest dial or response header timeout, and longest websocket close delay, in seconds that a domain may set, from 60 to 86400. A lowered value also tightens tuning already stored on the next ingress pass. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set domains.tuning_max_timeout_seconds | Settings > Runtime, Networking card |
domains.tuning_min_timeout_seconds | int | 1 | value must be between 1 and 60 | APP_DOMAIN_TUNING_MIN_TIMEOUT_SECONDS | yes | Shortest dial, response header, stream lifetime or stream close delay in seconds that a domain may set with domains tuning set, from 1 to 60, so it can never pass the longest timeout. A value of 0 on the domain keeps the ingress default. | levelrail-cli settings runtime get|set domains.tuning_min_timeout_seconds | Settings > Runtime, Networking card |
domains.www_mode | string | both | must be one of [both apex_only www_only] | APP_DOMAINS_WWW_MODE | yes | Which hosts get DNS records when a bare domain is planned: both (www follows the apex), apex_only or www_only. The next plan uses a changed value. | levelrail-cli settings runtime get|set domains.www_mode | Settings > Runtime, Networking card |
games.status_cache | duration | 5s | any valid duration | APP_GAME_STATUS_CACHE | yes | How long one game server status answer is reused, so many dashboards and CLI calls ping a game port at most once in this time. 0s turns the cache off. | levelrail-cli settings runtime get|set games.status_cache | Settings > Runtime, Networking card |
games.status_timeout | duration | 3s | any valid duration | APP_GAME_STATUS_TIMEOUT | yes | How long the game server status ping waits for a game port to answer before reporting it offline. Values under 200ms are raised to 200ms. | levelrail-cli settings runtime get|set games.status_timeout | Settings > Runtime, Networking card |
ingress.ca_switch_retry_base | duration | 1m | any valid duration | APP_INGRESS_CA_RETRY_BACKOFF | yes | First wait before retrying a certificate authority switch that failed to load; it doubles on each failure up to the maximum. | levelrail-cli settings runtime get|set ingress.ca_switch_retry_base | Settings > Runtime, Networking card |
ingress.ca_switch_retry_max | duration | 1h | any valid duration | APP_INGRESS_CA_RETRY_BACKOFF_MAX | yes | Upper bound on the wait between retries of a failed certificate authority switch. | levelrail-cli settings runtime get|set ingress.ca_switch_retry_max | Settings > Runtime, Networking card |
ingress.cloudflare_ips_max_bytes | int | 1048576 | value must be between 4096 and 16777216 | APP_CLOUDFLARE_IPS_MAX_BYTES | yes | Largest answer in bytes accepted from the Cloudflare address endpoint, from 4096 to 16 MiB. | levelrail-cli settings runtime get|set ingress.cloudflare_ips_max_bytes | Settings > Runtime, Networking card |
ingress.cloudflare_ips_min_ranges | int | 10 | value must be between 1 and 1000 | APP_CLOUDFLARE_IPS_MIN_RANGES | yes | A fetched Cloudflare list with fewer ranges than this is treated as truncated and ignored, so a bad answer cannot shrink the trusted set. | levelrail-cli settings runtime get|set ingress.cloudflare_ips_min_ranges | Settings > Runtime, Networking card |
ingress.cloudflare_ips_refresh | duration | 24h | value must be a duration between 1h0m0s and 720h0m0s | APP_CLOUDFLARE_IPS_REFRESH | yes | How often the Cloudflare address list is fetched from Cloudflare’s official endpoint, from 1h to 720h. The list shipped in the binary is used until the first fetch succeeds, and the last good list is kept when a fetch fails. | levelrail-cli settings runtime get|set ingress.cloudflare_ips_refresh | Settings > Runtime, Networking card |
ingress.cloudflare_ips_timeout | duration | 15s | value must be a duration between 1s and 2m0s | APP_CLOUDFLARE_IPS_TIMEOUT | yes | How long one fetch of the Cloudflare address list may take, from 1s to 2m. | levelrail-cli settings runtime get|set ingress.cloudflare_ips_timeout | Settings > Runtime, Networking card |
ingress.diagnostic_cache_ttl_seconds | int | 5 | value must be between 1 and 3600 | LEVELRAIL_INGRESS_DIAGNOSTIC_CACHE_TTL_SECONDS | yes | How often the host state snapshot refreshes, in seconds, minimum 1. Requests read the snapshot and never query the database. Idle while the show state setting is off. Read live; the environment variable only seeds the default. | levelrail-cli settings runtime get|set ingress.diagnostic_cache_ttl_seconds | Settings > Runtime, Networking card |
ingress.diagnostic_show_state | bool | false | any valid bool | LEVELRAIL_INGRESS_DIAGNOSTIC_SHOW_STATE | yes | When on, the ‘no app is serving this address’ page tells anyone who knows a hostname whether it is attached and its deploy state (building, stopped, starting, unhealthy). Off by default: every host then gets the same generic 404 page. Enable only on hosts where that disclosure is acceptable. Applies live. | levelrail-cli settings runtime get|set ingress.diagnostic_show_state | Settings > Runtime, Networking card |
ingress.dns01_all_hosts | bool | false | any valid bool | APP_INGRESS_DNS01_ALL_HOSTS | yes | Issue certificates for single hosts over DNS-01 as well as wildcards, so servers with port 80 closed can still get one. Needs a connected DNS provider; not yet verified against a real CA. | levelrail-cli settings runtime get|set ingress.dns01_all_hosts | Settings > Runtime, Networking card |
ingress.fallback_certs | string | eager | one of eager, lazy | APP_INGRESS_FALLBACK_CERTS | yes | When an app has no domain and gets an automatic sslip.io style hostname, eager orders its certificate as soon as the route exists (today’s behavior) and lazy orders it on the first TLS request for that hostname. Lazy keeps a burst of new apps from spending certificate rate limits on hosts nobody opens. A saved change re-renders the ingress config at once, with no restart; domains you configured yourself are always eager. | levelrail-cli settings runtime get|set ingress.fallback_certs | Settings > Runtime, Networking card |
ingress.max_body_bytes | int | 1073741824 | value must be between 1048576 and 10737418240 | APP_INGRESS_MAX_BODY_BYTES | yes | Largest request body in bytes the ingress accepts for each route before answering HTTP 413, from 1 MiB to 10 GiB. A saved change re-renders the ingress config at once, with no restart; a per-app override still applies. An environment value below the minimum is raised to it and 0 no longer disables the cap. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set ingress.max_body_bytes | Settings > Runtime, Networking card |
ingress.proxy_cert_wait | duration | 5m0s | value must be a duration between 1m0s and 24h0m0s | APP_PROXY_CERT_WAIT | yes | How long a domain behind an existing proxy may be without a certificate before the status says the proxy is stuck instead of still requesting one, from 1m to 24h. The dashboard also rechecks on its own for this long; a change applies on the next check. | levelrail-cli settings runtime get|set ingress.proxy_cert_wait | Settings > Runtime, Networking card |
ingress.trusted_proxy_preset | string | none | one of none, cloudflare | APP_INGRESS_TRUSTED_PROXY_PRESET | yes | cloudflare makes the ingress take the visitor address from CF-Connecting-IP, but only when the connection comes from Cloudflare’s published ranges (kept current in the background); a spoofed header from any other peer is ignored. Any Cloudflare customer can reach your server through a proxied record of their own, so this does not prove a request came through your zone. APP_INGRESS_TRUSTED_PROXIES entries stay trusted as well. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set ingress.trusted_proxy_preset | Settings > Runtime, Networking card |
ingress.unmatched_mode | string | diagnostic | one of diagnostic, not_found, redirect | APP_INGRESS_UNMATCHED_MODE | yes | What the ingress answers for a host no app claims, including the bare server address. diagnostic shows the help page, not_found answers a plain 404 with no detail, redirect sends visitors to the URL in ingress.unmatched_redirect_url. A saved change re-renders the ingress config at once, with no restart. | levelrail-cli settings runtime get|set ingress.unmatched_mode | Settings > Runtime, Networking card |
ingress.unmatched_redirect_url | string | empty | must be an absolute http or https URL | APP_INGRESS_UNMATCHED_REDIRECT_URL | yes | HTTP or HTTPS URL that unmatched hosts are redirected to when ingress.unmatched_mode is redirect. Empty with redirect mode falls back to the diagnostic page. A saved change re-renders the ingress config at once. | levelrail-cli settings runtime get|set ingress.unmatched_redirect_url | Settings > Runtime, Networking card |
mesh.apply_retries | int | 2 | value must be between 0 and 5 | APP_MESH_APPLY_RETRIES | yes | How many more times, from 0 to 5, the control plane resends a node its mesh config when the agent session dropped mid push, using the node’s new session. A timeout or a node that is not connected is not retried. The next pass uses a changed value. | levelrail-cli settings runtime get|set mesh.apply_retries | Settings > Runtime, Networking card |
mesh.apply_retry_delay | duration | 500ms | value must be a duration between 50ms and 10s | APP_MESH_APPLY_RETRY_DELAY | yes | The wait before the first mesh config retry, from 50ms to 10s. Each further retry waits twice as long, up to the push timeout. The next pass uses a changed value. | levelrail-cli settings runtime get|set mesh.apply_retry_delay | Settings > Runtime, Networking card |
mesh.apply_timeout | duration | 10s | value must be a duration between 1s and 5m0s | APP_MESH_APPLY_TIMEOUT | yes | The longest one attempt to send a node its WireGuard mesh config may take, from 1s to 5m. An agent that does not answer in time is not retried: it is marked unreachable for this pass so the rest of the fleet still converges, and the next pass sends it the current config. The next pass uses a changed value. | levelrail-cli settings runtime get|set mesh.apply_timeout | Settings > Runtime, Networking card |
mesh.hub_resolve_ttl | duration | 5m | value must be a duration between 30s and 24h0m0s | APP_MESH_HUB_RESOLVE_TTL | yes | When the advertise address is a hostname, the control plane resolves it to an IP for the mesh endpoint and checks again after this long. A changed DNS answer reaches agents on the next mesh reconcile; a failed lookup keeps the last good IP. Each lookup is bounded by the DNS lookup timeout (APP_DNS_STATUS_LOOKUP_TIMEOUT, shared with the DNS status checks). | levelrail-cli settings runtime get|set mesh.hub_resolve_ttl | Settings > Runtime, Networking card |
mesh.hub_stale_max | duration | 24h | value must be a duration between 5m0s and 720h0m0s | APP_MESH_HUB_STALE_MAX | yes | How long agents keep dialing the last good IP of the advertise hostname while lookups fail. After this the mesh endpoint is dropped, so a reused cloud IP does not receive handshakes meant for this server. | levelrail-cli settings runtime get|set mesh.hub_stale_max | Settings > Runtime, Networking card |
mesh.ready_retry_seconds | int | 10 | value must be between 2 and 300 | APP_MESH_READY_RETRY_SECONDS | yes | The longest gap, in seconds from 2 to 300, between checks of an app waiting for its node’s WireGuard mesh. Checks start at 2 seconds and double up to this value; the app starts as soon as the mesh is healthy. The next check uses a changed value. | levelrail-cli settings runtime get|set mesh.ready_retry_seconds | Settings > Runtime, Networking card |
mesh.wake_debounce | duration | 1s | value must be a duration between 100ms and 30s | APP_MESH_WAKE_DEBOUNCE | yes | When a node connects, disconnects or reconnects from a new address, the control plane waits this long and then runs one reconcile pass, so the mesh updates in seconds instead of on the next resync. Joins inside the window share one pass. The next join uses a changed value. | levelrail-cli settings runtime get|set mesh.wake_debounce | Settings > Runtime, Networking card |
models.hf_max_listed_files | int | 100 | value must be between 1 and 10000 | APP_HF_MAX_LISTED_FILES | yes | Most files a model preflight lists before it marks the list truncated. From 1 to 10000. | levelrail-cli settings runtime get|set models.hf_max_listed_files | Settings > Runtime, Networking card |
models.hf_max_response_bytes | int | 16777216 | value must be between 1048576 and 1073741824 | APP_HF_MAX_RESPONSE_BYTES | yes | Largest model hub listing response in bytes, from 1 MiB to 1 GiB. The next fetch uses a changed value. | levelrail-cli settings runtime get|set models.hf_max_response_bytes | Settings > Runtime, Networking card |
models.hf_timeout_seconds | int | 10 | value must be between 1 and 300 | APP_HF_TIMEOUT_SECONDS | no, restart | Seconds one model hub request may take. From 1 to 300. The client is built at startup, so a change needs a restart. | levelrail-cli settings runtime get|set models.hf_timeout_seconds | Settings > Runtime, Networking card |
net.outbound_timeout | duration | 30s | any valid duration | APP_NET_OUTBOUND_TIMEOUT | yes | How long an outbound HTTP request from the control plane (cloud metadata, model probes, upgrade checks) may take before it is cancelled. | levelrail-cli settings runtime get|set net.outbound_timeout | Settings > Runtime, Networking card |
network.gc_max_removals | int | 20 | value must be between 1 and 1000 | APP_NETWORK_GC_MAX_REMOVALS | yes | The most orphaned app networks one cleanup pass removes on a node, from 1 to 1000. Only networks labeled with this control plane are ever removed. The next pass uses a changed value. | levelrail-cli settings runtime get|set network.gc_max_removals | Settings > Runtime, Networking card |
pipelines.oidc_listen_port | int | 9095 | value must be between 1 and 65535 | APP_OIDC_LISTEN_PORT | no, restart | Port of the job OIDC endpoint on the Docker bridge gateway, from 1 to 65535. Change it when a second control plane on the same host holds the default. Read when the listener starts. | levelrail-cli settings runtime get|set pipelines.oidc_listen_port | Settings > Runtime, Networking card |
proxy.unrouted_to_levelrail | bool | false | any valid bool | LEVELRAIL_PROXY_UNROUTED_TO_LEVELRAIL | yes | Write a low priority catch-all route so hosts no router claims reach the Levelrail diagnostic page instead of a bare proxy 503. Traefik only. Hosts with no Traefik router are then served by the Levelrail ingress over plain HTTP, with no HTTPS redirect. It also catches hosts of other apps on the same front proxy when they have no router at all. Applies on the next route sync. | levelrail-cli settings runtime get|set proxy.unrouted_to_levelrail | Settings > Runtime, Networking card |
security.trust_loopback_forwarded_headers | bool | true | any valid bool | APP_TRUST_LOOPBACK_FORWARDED | no, restart | Believe X-Forwarded-For when the request arrives from this host. Turn off when nothing local proxies to the control plane. | levelrail-cli settings runtime get|set security.trust_loopback_forwarded_headers | Settings > Runtime, Networking card |
shell.section_timeout | duration | 2s | value must be a duration between 200ms and 30s | APP_SHELL_SECTION_TIMEOUT | yes | How long one section of GET /api/v1/shell may take, from 200ms to 30s. A slower section is left out and the dashboard fetches it on its own. The next request uses a changed value. | levelrail-cli settings runtime get|set shell.section_timeout | Settings > Runtime, Networking card |
templates.import_max_bytes | int | 262144 | value must be between 4096 and 2097152 | APP_TEMPLATE_IMPORT_MAX_BYTES | yes | Largest compose file in bytes that a template import from a URL downloads, from 4096 to 2097152. A bigger file is refused. A change applies to the next import. | levelrail-cli settings runtime get|set templates.import_max_bytes | Settings > Runtime, Networking card |
templates.import_timeout | duration | 10s | value must be a duration between 1s and 1m0s | APP_TEMPLATE_IMPORT_TIMEOUT | yes | How long a template import from a URL may take in total, from 1s to 1m. A change applies to the next import. | levelrail-cli settings runtime get|set templates.import_timeout | Settings > Runtime, Networking card |
Deploys
| Key | Type | Default | Range | Env seed | Live | Description | CLI | Dashboard |
|---|---|---|---|---|---|---|---|---|
app.image_keep | int | 0 | must be 0 (follow the global count) or from 2 to 1000 | APP_IMAGE_KEEP | yes | Images each app keeps when it has no keep count of its own: 0 follows the images-kept setting, otherwise 2 to 1000. Live images, rollback pins and images a queued or held deploy needs are always kept. | levelrail-cli settings runtime get|set app.image_keep | Settings > Runtime, Deploys card |
app.image_keep_overrides | string | empty | must be a JSON object of app name to keep count: json: cannot unmarshal number into Go value of type map[string]int | none | yes | Keep counts set on single apps, as a JSON object of app name to count. Set them from each app’s deploy settings or the images retention CLI rather than by hand. | levelrail-cli settings runtime get|set app.image_keep_overrides | Settings > Runtime, Deploys card |
apps.env_apply_on_set | bool | false | any valid bool | APP_ENV_APPLY_ON_SET | yes | When on, env set and env import restart the app so the new values reach the running container, as if —apply was passed. Pass —no-apply to keep one change pending. Off by default; a change applies to the next command. | levelrail-cli settings runtime get|set apps.env_apply_on_set | Settings > Runtime, Deploys card |
apps.max_replicas_per_service | int | 100 | value must be between 1 and 1000 | APP_MAX_REPLICAS_PER_SERVICE | yes | Largest replica count the API accepts for one service when an app is created, updated or scaled; a bigger count is refused with HTTP 400. Between 1 and 1000; a change applies to the next request, running apps keep their count. | levelrail-cli settings runtime get|set apps.max_replicas_per_service | Settings > Runtime, Deploys card |
apps.size_presets | string | small=0.5:512Mi,medium=1:1Gi,large=2:2Gi,xlarge=4:4Gi | preset “-1” must look like name=cpu:memory | APP_SIZE_PRESETS | yes | Named sizes for apps and databases as name=cpu:memory pairs, for example small=0.5:512Mi,large=2:2Gi. Memory ends in Mi or Gi. Apps already running keep their limits until scaled. | levelrail-cli settings runtime get|set apps.size_presets | Settings > Runtime, Deploys card |
apps_run.cpu_limit_millis | int | 0 | value must be between 0 and 1048576 | APP_RUN_CPU_LIMIT_MILLIS | yes | CPU limit in thousandths of a core (1000 is one core) for the container of a one-off command run. 0 keeps the app’s own limit. | levelrail-cli settings runtime get|set apps_run.cpu_limit_millis | Settings > Runtime, Deploys card |
apps_run.max_concurrent_per_app | int | 3 | value must be between 1 and 100 | APP_RUN_MAX_CONCURRENT_PER_APP | yes | How many one-off command runs (apps run, jobs run, the dashboard Run card) may be active on one app at the same time. A new run past the cap is refused with 429. | levelrail-cli settings runtime get|set apps_run.max_concurrent_per_app | Settings > Runtime, Deploys card |
apps_run.max_timeout_seconds | int | 3600 | value must be between 1 and 86400 | APP_RUN_MAX_TIMEOUT_SECONDS | yes | The longest a one-off command run may last, in seconds. A longer requested timeout is lowered to this value, and the container is killed and removed when it is reached. | levelrail-cli settings runtime get|set apps_run.max_timeout_seconds | Settings > Runtime, Deploys card |
apps_run.memory_limit_mb | int | 0 | value must be between 0 and 1048576 | APP_RUN_MEMORY_LIMIT_MB | yes | Memory limit in MB for the container of a one-off command run. 0 keeps the app’s own limit. | levelrail-cli settings runtime get|set apps_run.memory_limit_mb | Settings > Runtime, Deploys card |
backup.local_root | string | empty | path must be an absolute directory other than / | APP_BACKUP_LOCAL_ROOT | yes | Absolute directory on the control plane that confines local backup targets. Empty uses backups/ under the data directory. The next backup or restore uses a changed value; target paths stay relative to it and cannot leave it. | levelrail-cli settings runtime get|set backup.local_root | Settings > Runtime, Deploys card |
boot.deferred_stages | bool | false | any valid bool | APP_BOOT_DEFERRED_STAGES | no, restart | Start heartbeat, dynamic DNS, monitors and disk history after the HTTP listener is up so the dashboard answers sooner. GET /readyz lists the stages still pending. Read at start. | levelrail-cli settings runtime get|set boot.deferred_stages | Settings > Runtime, Deploys card |
boot.event_recheck | duration | 3s | value must be a duration between 1s and 1h0m0s | APP_BOOT_EVENT_RECHECK | no, restart | How long after the first Docker event the control plane runs one more reconcile pass, from 1s to 1h. Read at start. | levelrail-cli settings runtime get|set boot.event_recheck | Settings > Runtime, Deploys card |
boot.rechecks | string_list | 3s:10s | colon separated list | APP_BOOT_RECHECKS | no, restart | Offsets after start, colon separated (for example 3s:10s), at which the control plane runs extra reconcile passes so routes are fixed when Docker publishes ports late after a host reboot. Each offset is at least 1s. Read at start. | levelrail-cli settings runtime get|set boot.rechecks | Settings > Runtime, Deploys card |
bootstrap_scripts.max_bytes | int | 65536 | size must be between 1 and 8388608 | APP_BOOTSTRAP_SCRIPT_MAX_BYTES | yes | Largest saved bootstrap script body, in bytes. Read on every create and update; the environment variable only seeds the default. | levelrail-cli settings runtime get|set bootstrap_scripts.max_bytes | Settings > Runtime, Deploys card |
bootstrap_scripts.max_count | int | 50 | count must be between 1 and 10000 | APP_BOOTSTRAP_SCRIPT_MAX_COUNT | yes | How many bootstrap scripts can be saved at once. Read on every create; the environment variable only seeds the default. | levelrail-cli settings runtime get|set bootstrap_scripts.max_count | Settings > Runtime, Deploys card |
build.cache_app_quota_gb | int | 0 | value must be between 0 and 10240 | APP_BUILD_CACHE_APP_QUOTA_GB | yes | GiB of builder cache mounts one app may keep, from 0 to 10240. After each build, an app over its quota loses its least recently used cache mounts until it fits. Cache held by a running build is never removed. 0 turns the quota off. | levelrail-cli settings runtime get|set build.cache_app_quota_gb | Settings > Runtime, Deploys card |
build.cache_per_app | bool | true | any valid bool | APP_BUILD_CACHE_PER_APP | yes | Give each app its own build cache for package stores and framework caches, so one app cannot evict another’s. Read on every build; the environment variable only seeds the default. | levelrail-cli settings runtime get|set build.cache_per_app | Settings > Runtime, Deploys card |
build.cache_reclaim_max_records | int | 50 | value must be between 1 and 1000 | APP_BUILD_CACHE_RECLAIM_MAX_RECORDS | yes | The most cache records one quota reclaim removes, from 1 to 1000, so a single run stays short. The rest is reclaimed after the next build. | levelrail-cli settings runtime get|set build.cache_reclaim_max_records | Settings > Runtime, Deploys card |
build.cache_reclaim_timeout | duration | 2m | value must be a duration between 10s and 30m0s | APP_BUILD_CACHE_RECLAIM_TIMEOUT | yes | How long one quota reclaim may take, from 10s to 30m. A reclaim that runs out of time stops, and what it already freed is still reported and audited. | levelrail-cli settings runtime get|set build.cache_reclaim_timeout | Settings > Runtime, Deploys card |
build.next_min_free_memory_mib | int | 2048 | value must be between 0 and 1048576 | APP_BUILD_NEXT_MIN_FREE_MEMORY_MIB | yes | Host memory in MiB below which a Next.js build logs a low memory warning. 0 turns the warning off. The build is never blocked. Read on every build. | levelrail-cli settings runtime get|set build.next_min_free_memory_mib | Settings > Runtime, Deploys card |
builds.memory_limit_mb | int | 0 | value must be 0 (auto) or between 256 and 1048576 MiB | APP_BUILD_MEMORY_MB | yes | Memory in MiB one build may use (256 to 1048576). 0 means auto: 60 percent of the host memory, at least 512 and always leaving a reserve for the control plane (APP_BUILD_MEMORY_PERCENT and APP_BUILD_MEMORY_RESERVE_MB tune the formula). The cap also limits swap, and Node builds get a matching —max-old-space-size. A change applies to the next build; running builds keep their limit. A saved per-app or global value from build limits still wins. | levelrail-cli settings runtime get|set builds.memory_limit_mb | Settings > Runtime, Deploys card |
builds.setting_value_max_bytes | int | 128 | value must be between 16 and 1024 | APP_BUILD_SETTING_VALUE_MAX_BYTES | yes | Longest Dockerfile path, target stage or provider an app’s build settings may store. From 16 to 1024. Checked when the settings are saved. | levelrail-cli settings runtime get|set builds.setting_value_max_bytes | Settings > Runtime, Deploys card |
compose.depends_on_timeout | duration | 120s | value must be a duration between 5s and 1h0m0s | APP_COMPOSE_DEPENDS_ON_TIMEOUT | yes | How long a compose service waits for a depends_on dependency to start, pass its health check or exit 0 before the deploy fails naming that dependency, from 5s to 1h; a change applies on the next reconcile pass. | levelrail-cli settings runtime get|set compose.depends_on_timeout | Settings > Runtime, Deploys card |
compose.repo_deploy_timeout | duration | 10m | value must be a duration between 30s and 2h0m0s | APP_COMPOSE_REPO_DEPLOY_TIMEOUT | yes | How long one push deploy of a compose app from git may take to fetch the repository and apply the file, from 30s to 2h. It runs apart from the webhook request, so a forge timeout never stops it halfway. | levelrail-cli settings runtime get|set compose.repo_deploy_timeout | Settings > Runtime, Deploys card |
compose.repo_file_max_bytes | int | 524288 | value must be between 1024 and 4194304 | APP_COMPOSE_REPO_FILE_MAX_BYTES | yes | Largest compose file a compose app deployed from a git repository may read from the checkout, in bytes. From 1024 to 4194304. A larger file fails the deploy. | levelrail-cli settings runtime get|set compose.repo_file_max_bytes | Settings > Runtime, Deploys card |
containers.log_max_files | int | 0 | value must be between 0 and 100 | APP_CONTAINER_LOG_MAX_FILES | yes | Rotated log files Docker keeps per container, for containers created or recreated after the change. 0 leaves the Docker default. | levelrail-cli settings runtime get|set containers.log_max_files | Settings > Runtime, Deploys card |
containers.log_max_size_mb | int | 0 | value must be between 0 and 10240 | APP_CONTAINER_LOG_MAX_SIZE_MB | yes | Largest json-file log before Docker rotates it, for containers created or recreated after the change. 0 leaves the Docker default and recreates nothing. Rotation needs both this and the file count above 0. | levelrail-cli settings runtime get|set containers.log_max_size_mb | Settings > Runtime, Deploys card |
containers.restart_policy | string | unless-stopped | one of unless-stopped, on-failure, no | APP_CONTAINERS_RESTART_POLICY | yes | Docker restart policy for long-running app containers, so apps come back after a host reboot or Docker restart. On a small host (1 GB) many apps starting at boot at once compete for memory; use no to rely on the control plane’s sequential start. Applies to containers created on the next deploy or recreate; existing containers keep their old policy. | levelrail-cli settings runtime get|set containers.restart_policy | Settings > Runtime, Deploys card |
databases.bulk_concurrency | int | 4 | value must be between 1 and 32 | APP_DATABASES_BULK_CONCURRENCY | yes | How many databases one bulk start, stop or backup (databases bulk, POST /api/v1/databases/bulk) acts on at once. From 1 to 32. The next bulk call uses a changed value. | levelrail-cli settings runtime get|set databases.bulk_concurrency | Settings > Runtime, Deploys card |
databases.bulk_max_items | int | 200 | value must be between 1 and 2000 | APP_DATABASES_BULK_MAX_ITEMS | yes | Most databases one bulk call may target; a bigger selection is refused with HTTP 400 and nothing runs. From 1 to 2000. The next bulk call uses a changed value. | levelrail-cli settings runtime get|set databases.bulk_max_items | Settings > Runtime, Deploys card |
databases.params_max_connections | int | 5000 | value must be between 10 and 1000000 | APP_DB_PARAMS_MAX_CONNECTIONS | yes | Highest max_connections, maxclients or maxConns a managed database may be tuned to, from 10 to 1000000. Applies to the next staged change. | levelrail-cli settings runtime get|set databases.params_max_connections | Settings > Runtime, Deploys card |
databases.params_max_memory_mb | int | 4096 | value must be between 64 and 1048576 | APP_DB_PARAMS_MAX_MEMORY_MB | yes | Highest memory size parameter, in MB, for a managed database with no memory limit, from 64 to 1048576. A database with a memory limit is capped at 75 percent of it instead. Applies when the database next restarts or a change is applied. | levelrail-cli settings runtime get|set databases.params_max_memory_mb | Settings > Runtime, Deploys card |
databases.pooler_default | string | off | one of off, on | APP_DATABASES_POOLER_DEFAULT | yes | When on, new Postgres databases get the connection pooler enabled at creation. Existing databases never change. Apps that rely on session features through the pooled url (prepared statements, SET, temp tables) should use direct_url. | levelrail-cli settings runtime get|set databases.pooler_default | Settings > Runtime, Deploys card |
databases.pooler_image | string | edoburu/pgbouncer:v1.26.1-p0 | must pin a version tag or digest, not latest | APP_PG_POOLER_IMAGE | yes | The pinned image tag or digest the connection pooler runs. It must speak the pgbouncer env contract. Applies to poolers created or reconciled after the change. | levelrail-cli settings runtime get|set databases.pooler_image | Settings > Runtime, Deploys card |
deploy.app_expiry_claim_ttl | duration | 1h0m0s | value must be between 5m0s and 24h0m0s | none | yes | How long a delete claim on an expired app may stay before the sweep treats it as abandoned and releases it. Between 5m and 24h. | levelrail-cli settings runtime get|set deploy.app_expiry_claim_ttl | Settings > Runtime, Deploys card |
deploy.app_expiry_delete_enabled | bool | false | any valid bool | none | yes | Off by default: expired apps are only noticed and stopped. Turn on to let the sweep delete them after the grace period. | levelrail-cli settings runtime get|set deploy.app_expiry_delete_enabled | Settings > Runtime, Deploys card |
deploy.app_expiry_grace_hours | int | 168 | value must be between 1 and 2160 | none | yes | Hours an expired app stays stopped before the sweep may delete it. Between 1 hour and 90 days. Clearing the expiry in that window cancels the delete. | levelrail-cli settings runtime get|set deploy.app_expiry_grace_hours | Settings > Runtime, Deploys card |
deploy.app_expiry_max_horizon_days | int | 90 | value must be between 1 and 3650 | none | yes | Furthest in the future an app expiry may be set. | levelrail-cli settings runtime get|set deploy.app_expiry_max_horizon_days | Settings > Runtime, Deploys card |
deploy.app_expiry_max_per_sweep | int | 20 | value must be between 1 and 500 | none | yes | Most apps one expiry sweep notifies, stops or deletes. The rest wait for the next sweep. | levelrail-cli settings runtime get|set deploy.app_expiry_max_per_sweep | Settings > Runtime, Deploys card |
deploy.app_expiry_notice_hours | int | 24 | value must be between 0 and 720 | none | yes | Hours before an app’s expiry that the notice is written to the audit log. The stop always waits for the notice. | levelrail-cli settings runtime get|set deploy.app_expiry_notice_hours | Settings > Runtime, Deploys card |
deploy.approval_claim_timeout_seconds | int | 900 | value must be between 30 and 86400 | APP_DEPLOY_APPROVAL_CLAIM_TIMEOUT_SECONDS | yes | Seconds an approving claim may stand before recovery treats its claimer as gone. From 30 to 86400. The next recovery pass uses a changed value. | levelrail-cli settings runtime get|set deploy.approval_claim_timeout_seconds | Settings > Runtime, Deploys card |
deploy.approval_max_required | int | 10 | value must be between 1 and 50 | APP_DEPLOY_APPROVAL_MAX_REQUIRED | yes | Highest number of distinct approvers a protected environment may require before a deploy is released. From 1 to 50. An environment set above a lowered value uses this value at release time. | levelrail-cli settings runtime get|set deploy.approval_max_required | Settings > Runtime, Deploys card |
deploy.approve_digest_check_timeout_seconds | int | 0 | value must be between 0 and 600 | APP_APPROVE_DIGEST_CHECK_TIMEOUT_SECONDS | yes | Seconds the registry digest check may take when an approval is granted. 0 uses the request deadline. From 0 to 600. | levelrail-cli settings runtime get|set deploy.approve_digest_check_timeout_seconds | Settings > Runtime, Deploys card |
deploy.build_hook_max_cidrs | int | 32 | value must be between 1 and 256 | APP_BUILD_HOOK_MAX_CIDRS | yes | Most source address ranges (CIDRs) one build hook’s allowlist may hold, from 1 to 256. Lowering it keeps longer lists already saved; the next edit must fit. | levelrail-cli settings runtime get|set deploy.build_hook_max_cidrs | Settings > Runtime, Deploys card |
deploy.build_hook_triggers_per_minute | int | 6 | value must be between 1 and 600 | APP_BUILD_HOOK_TRIGGERS_PER_MINUTE | yes | Most calls one build hook accepts per minute, from 1 to 600. Calls refused by the source allowlist use a separate bucket of the same size, so a blocked caller is throttled without using up the allowed budget. Over the limit the hook answers 429. The next call uses a changed value. | levelrail-cli settings runtime get|set deploy.build_hook_triggers_per_minute | Settings > Runtime, Deploys card |
deploy.ci_gate_max_waits_per_app | int | 4 | value must be between 1 and 50 | APP_CI_GATE_MAX_WAITS_PER_APP | yes | How many refs of one app may wait for CI at once. A newer deploy of the same ref replaces the wait; one past the limit is refused and can be retried. | levelrail-cli settings runtime get|set deploy.ci_gate_max_waits_per_app | Settings > Runtime, Deploys card |
deploy.drain_timeout | duration | 15s | value must be a duration between 1s and 10m0s | APP_DEPLOY_DRAIN_TIMEOUT | yes | How long the previous release keeps serving after a cutover so in-flight requests finish, from 1s to 10m. Below the longest request your app serves, a deploy can cut requests short. Read on every reconcile pass, so it applies to the next deploy; a per-app override still wins. | levelrail-cli settings runtime get|set deploy.drain_timeout | Settings > Runtime, Deploys card |
deploy.inline_source_keep | int | 10 | value must be between 1 and 1000 | APP_INLINE_SOURCE_KEEP | yes | How many distinct pasted Dockerfiles each app keeps for redeploys; the hourly sweep deletes older ones unless a queued, held or running deploy still needs them. Between 1 and 1000. A change applies to the next sweep. | levelrail-cli settings runtime get|set deploy.inline_source_keep | Settings > Runtime, Deploys card |
deploy.inline_source_max_bytes | int | 262144 | value must be between 1024 and 8388608 | APP_INLINE_SOURCE_MAX_BYTES | yes | Largest pasted Dockerfile plus extra context files, in bytes, accepted by a deploy without a git repository; a bigger one is refused with HTTP 413. Between 1 KiB and 8 MiB, and never more than the API request body limit. A change applies to the next deploy. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set deploy.inline_source_max_bytes | Settings > Runtime, Deploys card |
deploy.inline_source_max_files | int | 20 | value must be between 0 and 200 | APP_INLINE_SOURCE_MAX_FILES | yes | How many extra context files may be sent next to a pasted Dockerfile; more are refused with HTTP 413. 0 allows the Dockerfile alone. A change applies to the next deploy. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set deploy.inline_source_max_files | Settings > Runtime, Deploys card |
deploy.max_concurrent | int | 0 | value must be between 0 and 1000 | APP_DEPLOY_MAX_CONCURRENT | yes | How many deploys may run at once across all apps; extra deploys wait in the queue and start when one finishes. 0 means no limit. A change applies to the next queue decision. | levelrail-cli settings runtime get|set deploy.max_concurrent | Settings > Runtime, Deploys card |
deploy.max_concurrent_per_project | int | 0 | value must be between 0 and 1000 | APP_DEPLOY_MAX_CONCURRENT_PER_PROJECT | yes | How many deploys of apps in one project may run at once; extra deploys wait in the queue and start when one finishes. 0 means no limit. The host-wide limit still applies. A change applies to the next queue decision. | levelrail-cli settings runtime get|set deploy.max_concurrent_per_project | Settings > Runtime, Deploys card |
deploy.next_asset_grace_max_held | int | 1 | value must be between 1 and 3 | APP_DEPLOY_NEXT_ASSET_GRACE_MAX_HELD | yes | How many superseded Next.js releases per app stay running during the old asset grace window. Each one keeps its containers up, so it costs their memory and CPU for the whole window. 1 holds only the previous release. Read on every deploy. | levelrail-cli settings runtime get|set deploy.next_asset_grace_max_held | Settings > Runtime, Deploys card |
deploy.next_asset_grace_seconds | int | 1800 | value must be between 0 and 604800 | APP_DEPLOY_NEXT_ASSET_GRACE_SECONDS | yes | Seconds after a cutover during which the previous Next.js release keeps serving its old static chunks and data requests. 0 turns it off. Read on every deploy. | levelrail-cli settings runtime get|set deploy.next_asset_grace_seconds | Settings > Runtime, Deploys card |
deploy.next_deployment_id | bool | true | any valid bool | APP_DEPLOY_NEXT_DEPLOYMENT_ID | yes | Set NEXT_DEPLOYMENT_ID to the deploy id at build time and on the app containers of Next.js apps, so a browser tab on an old build can be matched to it. A value the app sets itself always wins. Read on every deploy; the environment variable only seeds the default. | levelrail-cli settings runtime get|set deploy.next_deployment_id | Settings > Runtime, Deploys card |
deploy.phases_samples | int | 5 | value must be between 2 and 50 | APP_DEPLOY_PHASES_SAMPLES | yes | How many recent successful deploys of an app are averaged into the typical phase times and the time left estimate, from 2 to 50. Read on every request; the environment variable only seeds the default. | levelrail-cli settings runtime get|set deploy.phases_samples | Settings > Runtime, Deploys card |
deploy.preview_cache_mode | string | isolated | one of isolated, shared_with_app, off | APP_DEPLOY_PREVIEW_CACHE_MODE | yes | How pull request preview builds use the BuildKit cache. isolated gives each preview its own cache, shared_with_app reuses the app’s cache (faster, but a preview can poison the production cache), off builds every preview with a fresh cache. Read on every preview build; the environment variable only seeds the default. | levelrail-cli settings runtime get|set deploy.preview_cache_mode | Settings > Runtime, Deploys card |
deploy.preview_ttl_hours | int | 0 | value must be between 0 and 8760 | none | yes | Hours a pull request preview may go without an update before the sweep removes it. 0 keeps the startup default. A per-app override still wins. Read on every sweep and listing. | levelrail-cli settings runtime get|set deploy.preview_ttl_hours | Settings > Runtime, Deploys card |
deploy.previous_release_hold | duration | 3m | value must be a duration between 0s and 1h0m0s | APP_DEPLOY_PREVIOUS_RELEASE_HOLD | yes | How long the previous release stays running after a cutover as an instant rollback target, from 0 (remove at once) to 1h. The effective hold is never shorter than the drain timeout, and with auto-rollback on it also covers the watch window. Applies on the next deploy. | levelrail-cli settings runtime get|set deploy.previous_release_hold | Settings > Runtime, Deploys card |
deploy.procfile_default_port | int | 8080 | value must be between 1 and 65535 | APP_DEPLOY_PROCFILE_DEFAULT_PORT | yes | The port given to the web process of an app deployed from a Procfile, since a Procfile cannot declare one, from 1 to 65535. The next deploy uses a changed value; apps already deployed keep their port. | levelrail-cli settings runtime get|set deploy.procfile_default_port | Settings > Runtime, Deploys card |
deploy.receipt_approval_window | duration | 15m | value must be a duration between 1m0s and 24h0m0s | APP_DEPLOY_RECEIPT_APPROVAL_WINDOW | yes | How long before a deploy started an approval may have been decided for the receipt to name it as the approval that released that deploy, from 1m to 24h. A longer window can name an approval meant for an earlier deploy. The next receipt uses a changed value. | levelrail-cli settings runtime get|set deploy.receipt_approval_window | Settings > Runtime, Deploys card |
deploy.restart_schedule_failure_backoff | duration | 15m0s | value must be between 1m0s and 24h0m0s | APP_RESTART_SCHEDULE_FAILURE_BACKOFF | yes | Wait before retrying a scheduled restart that failed, doubled per consecutive failure up to 24h, and never later than the next regular run. Between 1m and 24h. | levelrail-cli settings runtime get|set deploy.restart_schedule_failure_backoff | Settings > Runtime, Deploys card |
deploy.restart_schedule_max_per_sweep | int | 5 | value must be between 1 and 100 | APP_RESTART_SCHEDULE_MAX_PER_SWEEP | yes | Most apps one control plane restarts in one scheduled restart sweep. The rest wait for the next sweep. | levelrail-cli settings runtime get|set deploy.restart_schedule_max_per_sweep | Settings > Runtime, Deploys card |
deploy.restart_schedule_min_interval | duration | 1h0m0s | value must be between 5m0s and 168h0m0s | APP_RESTART_SCHEDULE_MIN_INTERVAL | yes | Shortest gap allowed between two scheduled restarts of one app, so a schedule cannot restart-loop an app. Between 5m and 168h. | levelrail-cli settings runtime get|set deploy.restart_schedule_min_interval | Settings > Runtime, Deploys card |
deploy.stable_window | duration | 10s | value must be a duration between 1s and 10m0s | APP_DEPLOY_STABLE_WINDOW | yes | How long a new container must stay running with no restart or OOM kill before it takes traffic, from 1s to 10m. Applies on the next deploy; a per-app override still wins. | levelrail-cli settings runtime get|set deploy.stable_window | Settings > Runtime, Deploys card |
deploy.watch_window | duration | 5m | value must be a duration between 0s and 24h0m0s | APP_DEPLOY_WATCH_WINDOW | yes | How long a new release is watched for restarts and 5xx before it counts as healthy, from 0 (no watch) to 24h. Auto-rollback needs the previous release held for this long. Applies to the next evaluation; a per-app override still wins. | levelrail-cli settings runtime get|set deploy.watch_window | Settings > Runtime, Deploys card |
deploys.registry_push_debounce | duration | 30s | value must be a duration between 1s and 10m0s | APP_REGISTRY_PUSH_DEBOUNCE | yes | Minimum spacing between registry lookups the image-update webhook makes for unsigned push deliveries, and how long it skips the plain hook and a signed repeat of the digest it just handled, so retries do not hammer the registry. | levelrail-cli settings runtime get|set deploys.registry_push_debounce | Settings > Runtime, Deploys card |
deploys.registry_push_max_body_bytes | int | 262144 | value must be between 1024 and 4194304 | APP_REGISTRY_PUSH_MAX_BODY_BYTES | yes | Largest registry push payload, in bytes, the image-update webhook reads before refusing it, from 1024 to 4194304. | levelrail-cli settings runtime get|set deploys.registry_push_max_body_bytes | Settings > Runtime, Deploys card |
deploys.registry_push_timeout | duration | 5m | value must be a duration between 10s and 1h0m0s | APP_REGISTRY_PUSH_TIMEOUT | yes | How long one registry push may spend resolving and deploying its digest before it is abandoned. | levelrail-cli settings runtime get|set deploys.registry_push_timeout | Settings > Runtime, Deploys card |
git.poll_concurrency | int | 4 | any valid int | APP_GIT_POLL_CONCURRENCY | yes | How many git sources are checked at the same time. | levelrail-cli settings runtime get|set git.poll_concurrency | Settings > Runtime, Deploys card |
git.poll_enabled | bool | true | any valid bool | APP_GIT_POLL_ENABLED | yes | Compare each auto-deploy git source with its remote branch and queue a deploy when a webhook was missed. | levelrail-cli settings runtime get|set git.poll_enabled | Settings > Runtime, Deploys card |
git.poll_interval | duration | 5m | any valid duration | APP_GIT_POLL_INTERVAL | yes | How often each git source is checked for a missed push. | levelrail-cli settings runtime get|set git.poll_interval | Settings > Runtime, Deploys card |
git.poll_max_backoff | duration | 1h | any valid duration | APP_GIT_POLL_MAX_BACKOFF | yes | The longest wait before a failing or rate limited git source is checked again. | levelrail-cli settings runtime get|set git.poll_max_backoff | Settings > Runtime, Deploys card |
git.submodules_max_count | int | 32 | value must be between 1 and 256 | APP_GIT_SUBMODULES_MAX_COUNT | yes | Most submodules, at every depth together, one git source build fetches, from 1 to 256. | levelrail-cli settings runtime get|set git.submodules_max_count | Settings > Runtime, Deploys card |
git.submodules_max_depth | int | 3 | value must be between 1 and 10 | APP_GIT_SUBMODULES_MAX_DEPTH | yes | How deep submodules of a git source build may nest, from 1 to 10. A deeper tree fails the build with a clear error. | levelrail-cli settings runtime get|set git.submodules_max_depth | Settings > Runtime, Deploys card |
git.submodules_max_mb | int | 4096 | value must be between 16 and 65536 | APP_GIT_SUBMODULES_MAX_MB | yes | Largest checkout in MB, repository plus submodules plus LFS objects, from 16 to 65536. A bigger checkout fails the build. | levelrail-cli settings runtime get|set git.submodules_max_mb | Settings > Runtime, Deploys card |
git.submodules_timeout | duration | 10m | value must be a duration between 10s and 1h0m0s | APP_GIT_SUBMODULES_TIMEOUT | yes | How long fetching all submodules and LFS objects of one build may take, from 10s to 1h. | levelrail-cli settings runtime get|set git.submodules_timeout | Settings > Runtime, Deploys card |
git.trigger_pattern_list_max_bytes | int | 1024 | value must be between 64 and 4096 | APP_GIT_TRIGGER_PATTERN_LIST_MAX_BYTES | yes | Most bytes all tag or branch patterns of one list may total, which bounds the matching cost of each push. From 64 to 4096. Checked when the list is saved. | levelrail-cli settings runtime get|set git.trigger_pattern_list_max_bytes | Settings > Runtime, Deploys card |
git.trigger_pattern_max_length | int | 128 | value must be between 8 and 1024 | APP_GIT_TRIGGER_PATTERN_MAX_LENGTH | yes | Longest tag or branch pattern in bytes. From 8 to 1024. Checked when the pattern is saved. | levelrail-cli settings runtime get|set git.trigger_pattern_max_length | Settings > Runtime, Deploys card |
git.trigger_patterns_max | int | 32 | value must be between 1 and 256 | APP_GIT_TRIGGER_PATTERNS_MAX | yes | Most tag or branch patterns one git source may set. From 1 to 256. Saved lists over a lowered value keep working until edited. | levelrail-cli settings runtime get|set git.trigger_patterns_max | Settings > Runtime, Deploys card |
git.trigger_ref_max_bytes | int | 1024 | value must be between 64 and 4096 | APP_GIT_TRIGGER_REF_MAX_BYTES | yes | Longest pushed ref a trigger pattern is matched against; a longer ref never deploys. From 64 to 4096. | levelrail-cli settings runtime get|set git.trigger_ref_max_bytes | Settings > Runtime, Deploys card |
iac.plan_value_max | int | 120 | value must be between 20 and 10000 | APP_IAC_PLAN_VALUE_MAX | yes | Longest before or after value a plan shows, in characters. From 20 to 10000. The next plan uses a changed value. | levelrail-cli settings runtime get|set iac.plan_value_max | Settings > Runtime, Deploys card |
images.keep_per_app | int | 3 | value must be between 1 and 1000 | APP_IMAGE_KEEP_PER_APP | yes | How many recent images of each app the image cleanup keeps for rollback, at least 1. Live images and rollback pins are always kept. Applies to the next cleanup, manual or scheduled. | levelrail-cli settings runtime get|set images.keep_per_app | Settings > Runtime, Deploys card |
images.prune_schedule | string | off | must be “off” or a valid cron expression such as 0 3 * * 0: cronexpr: expected 5 fields (minute hour day-of-month month day-of-week), got 1 in “-1” | none | yes | A cron expression (for example 0 3 * * 0 for Sundays at 03:00) for removing old images on this node, or off. The cleanup uses the same safety rules as the manual one and the images-kept setting. Off by default. | levelrail-cli settings runtime get|set images.prune_schedule | Settings > Runtime, Deploys card |
images.pull_concurrency | int | 3 | value must be between 1 and 32 | APP_IMAGES_PULL_CONCURRENCY | yes | Most distinct image pulls a node runs at the same time, from 1 to 32. Deploys that need the same image share one pull. | levelrail-cli settings runtime get|set images.pull_concurrency | Settings > Runtime, Deploys card |
jobs.failure_alert_batch | int | 50 | value must be between 1 and 1000 | APP_JOBS_FAILURE_ALERT_BATCH | yes | Most failing jobs one job_failing alert rule reports per evaluation. Read on every run; the environment variable only seeds the default. | levelrail-cli settings runtime get|set jobs.failure_alert_batch | Settings > Runtime, Deploys card |
jobs.failure_alert_window_seconds | int | 3600 | value must be between 60 and 604800 | APP_JOBS_FAILURE_ALERT_WINDOW_SECONDS | yes | Seconds between two failure alerts for the same job; failures inside the window are only in history. Read on every run; the environment variable only seeds the default. | levelrail-cli settings runtime get|set jobs.failure_alert_window_seconds | Settings > Runtime, Deploys card |
jobs.http_timeout_seconds | int | 30 | value must be between 1 and 3600 | APP_JOBS_HTTP_TIMEOUT_SECONDS | yes | Seconds an HTTP job waits for its app to answer when the job sets no timeout of its own. Read on every run; the environment variable only seeds the default. | levelrail-cli settings runtime get|set jobs.http_timeout_seconds | Settings > Runtime, Deploys card |
jobs.retention_max_days | int | 365 | value must be between 1 and 3650 | APP_JOBS_RETENTION_MAX_DAYS | yes | Oldest run age in days kept per job, whatever the job’s own keep days value says. Read on every run; the environment variable only seeds the default. | levelrail-cli settings runtime get|set jobs.retention_max_days | Settings > Runtime, Deploys card |
jobs.retention_max_runs | int | 1000 | value must be between 1 and 100000 | APP_JOBS_RETENTION_MAX_RUNS | yes | Most runs kept per job, whatever the job’s own keep runs value says. Read on every run; the environment variable only seeds the default. | levelrail-cli settings runtime get|set jobs.retention_max_runs | Settings > Runtime, Deploys card |
jobs.retention_skipped_keep | int | 20 | value must be between 1 and 1000 | APP_JOBS_RETENTION_SKIPPED_KEEP | yes | Skipped runs kept per job, counted apart from real runs so overlap skips never push real history out. Read on every run; the environment variable only seeds the default. | levelrail-cli settings runtime get|set jobs.retention_skipped_keep | Settings > Runtime, Deploys card |
jobs.retention_sweep_max_rows | int | 500 | value must be between 1 and 100000 | APP_JOBS_RETENTION_SWEEP_MAX_ROWS | yes | Most history rows one prune pass deletes, so pruning a large backlog never locks the database for long. Read on every run; the environment variable only seeds the default. | levelrail-cli settings runtime get|set jobs.retention_sweep_max_rows | Settings > Runtime, Deploys card |
jobs.timeout_max_seconds | int | 86400 | value must be between 1 and 604800 | APP_JOBS_TIMEOUT_MAX_SECONDS | yes | Longest timeout in seconds a scheduled job attempt may use; the run is stopped at this even when the job asks for more. Read on every run; the environment variable only seeds the default. | levelrail-cli settings runtime get|set jobs.timeout_max_seconds | Settings > Runtime, Deploys card |
jobs.timeout_min_seconds | int | 1 | value must be between 1 and 86400 | APP_JOBS_TIMEOUT_MIN_SECONDS | yes | Shortest timeout in seconds a scheduled job attempt may use; a shorter per-job timeout is raised to this. Read on every run; the environment variable only seeds the default. | levelrail-cli settings runtime get|set jobs.timeout_min_seconds | Settings > Runtime, Deploys card |
nextjs.generate_actions_key | bool | true | any valid bool | APP_NEXTJS_GENERATE_ACTIONS_KEY | yes | When the wizard deploys a Next.js app (version 14 or newer) that has no NEXT_SERVER_ACTIONS_ENCRYPTION_KEY, Levelrail generates a random key once, stores it as an app secret and gives it to every replica at runtime so Server Actions keep working across replicas and redeploys. Existing apps are never changed, and a redeploy never rotates the key. Delete the secret to rotate it. The key is not passed to builds. | levelrail-cli settings runtime get|set nextjs.generate_actions_key | Settings > Runtime, Deploys card |
nextjs.memory_floor_mb | int | 256 | value must be between 0 and 65536 | none | yes | The doctor warns when a Next.js app has a memory limit below this many MiB, because the server risks being killed for running out of memory. 0 turns the warning off. The warning is advisory and never blocks a deploy. | levelrail-cli settings runtime get|set nextjs.memory_floor_mb | Settings > Runtime, Deploys card |
placement.affinity_max_terms | int | 8 | value must be between 1 and 64 | APP_PLACEMENT_AFFINITY_MAX_TERMS | yes | Most affinity terms one app may carry. From 1 to 64. Saved rules are kept when the value is lowered. | levelrail-cli settings runtime get|set placement.affinity_max_terms | Settings > Runtime, Deploys card |
placement.score_mode | string | spread | one of spread, binpack | APP_PLACEMENT_SCORE_MODE | yes | How new workloads pick a node: spread keeps the most headroom free on each node, binpack fills the fullest node that still fits. Failure-domain spread (zone labels) is applied first; the mode orders nodes inside a domain. Read on every placement; the environment variable only seeds the default. | levelrail-cli settings runtime get|set placement.score_mode | Settings > Runtime, Deploys card |
previews.migrate_timeout | duration | 10m | value must be a duration between 10s and 24h0m0s | APP_PREVIEW_MIGRATE_TIMEOUT | yes | How long a preview migration command may run before the preview fails, from 10s to 24h. An app’s own timeout still wins. The next preview uses a changed value. | levelrail-cli settings runtime get|set previews.migrate_timeout | Settings > Runtime, Deploys card |
previews.migrate_wait | duration | 2m | value must be a duration between 5s and 1h0m0s | APP_PREVIEW_MIGRATE_WAIT | yes | How long a preview migration waits for the preview container to appear before giving up, from 5s to 1h. The next preview uses a changed value. | levelrail-cli settings runtime get|set previews.migrate_wait | Settings > Runtime, Deploys card |
projects.clone_max_apps | int | 50 | value must be between 1 and 1000 | APP_PROJECT_CLONE_MAX_APPS | yes | The most apps one project clone may copy, from 1 to 1000. A project with more apps is refused with a clear message. The next clone uses a changed value. | levelrail-cli settings runtime get|set projects.clone_max_apps | Settings > Runtime, Deploys card |
projects.clone_placeholder_domain | string | clone.invalid | any valid string | APP_PROJECT_CLONE_PLACEHOLDER_DOMAIN | yes | The domain suffix given to copied domains when a clone uses placeholder domains, so the copy never claims the real hostnames. The default is a reserved name that never resolves. The next clone uses a changed value. | levelrail-cli settings runtime get|set projects.clone_placeholder_domain | Settings > Runtime, Deploys card |
projects.default_environment | bool | false | any valid bool | APP_PROJECTS_DEFAULT_ENVIRONMENT | yes | When on, a new project starts with one unprotected default environment, and an app or database created in a project without naming an environment joins it. The next project uses a changed value. | levelrail-cli settings runtime get|set projects.default_environment | Settings > Runtime, Deploys card |
projects.default_environment_name | string | production | must be 1 to 63 letters, digits, spaces, dots, dashes or underscores, starting with a letter or digit | APP_PROJECTS_DEFAULT_ENVIRONMENT_NAME | yes | Name given to the default environment of a new project. The next project uses a changed value. | levelrail-cli settings runtime get|set projects.default_environment_name | Settings > Runtime, Deploys card |
registry.mirror_prefix | string | empty | must be a hostname with an optional path, for example m.daocloud.io | APP_REGISTRY_MIRROR_PREFIX | yes | A hostname, with an optional path and no scheme, put in front of the registry host when pulling the node agent and BuildKit images, for example m.daocloud.io. Digest pins are kept. Empty pulls directly. Read when a node is provisioned or the build daemon starts; the environment variable only seeds the default. | levelrail-cli settings runtime get|set registry.mirror_prefix | Settings > Runtime, Deploys card |
resources.description_max_chars | int | 280 | value must be between 1 and 2000 | APP_RESOURCE_DESCRIPTION_MAX_CHARS | yes | Most characters in the one line description of an app or database. From 1 to 2000. Saved descriptions are kept when the value is lowered. | levelrail-cli settings runtime get|set resources.description_max_chars | Settings > Runtime, Deploys card |
resources.notes_max_bytes | int | 65536 | value must be between 1024 and 1048576 | APP_RESOURCE_NOTES_MAX_BYTES | yes | Most bytes of markdown notes on an app or database. From 1024 to 1048576. Saved notes are kept when the value is lowered. | levelrail-cli settings runtime get|set resources.notes_max_bytes | Settings > Runtime, Deploys card |
runtime.dns_max | int | 3 | value must be between 1 and 16 | APP_RUNTIME_DNS_MAX | yes | Most DNS resolvers a container may have in total, from 1 to 16. A change applies to the next deploy or runtime edit; running containers keep their options until recreated. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set runtime.dns_max | Settings > Runtime, Deploys card |
runtime.extra_hosts_max | int | 32 | value must be between 1 and 256 | APP_RUNTIME_EXTRA_HOSTS_MAX | yes | Most extra_hosts entries one service may declare, from 1 to 256. A change applies to the next deploy or runtime edit; running containers keep their options until recreated. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set runtime.extra_hosts_max | Settings > Runtime, Deploys card |
runtime.pids_limit_max | int | 32768 | value must be between 1 and 4194304 | APP_RUNTIME_PIDS_LIMIT_MAX | yes | Largest pids_limit one service may request, from 1 to 4194304. A change applies to the next deploy or runtime edit; running containers keep their options until recreated. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set runtime.pids_limit_max | Settings > Runtime, Deploys card |
runtime.shm_max_bytes | int | 4294967296 | value must be between 1048576 and 68719476736 | APP_RUNTIME_SHM_MAX_BYTES | yes | Largest shm_size in bytes one service may request, from 1 MiB to 64 GiB. A change applies to the next deploy or runtime edit; running containers keep their options until recreated. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set runtime.shm_max_bytes | Settings > Runtime, Deploys card |
runtime.stop_timeout_max_seconds | int | 600 | value must be between 1 and 3600 | APP_RUNTIME_STOP_TIMEOUT_MAX_SECONDS | yes | Longest stop timeout in seconds a service may ask for, from 1 to 3600. A change applies to the next deploy or runtime edit; running containers keep their options until recreated. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set runtime.stop_timeout_max_seconds | Settings > Runtime, Deploys card |
runtime.tmpfs_default_bytes | int | 67108864 | value must be between 1048576 and 68719476736 | APP_RUNTIME_TMPFS_DEFAULT_BYTES | yes | Size in bytes given to a compose tmpfs entry that has no size, capped by the tmpfs size limit. From 1 MiB to 64 GiB. A change applies to the next deploy or runtime edit; running containers keep their options until recreated. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set runtime.tmpfs_default_bytes | Settings > Runtime, Deploys card |
runtime.tmpfs_max | int | 16 | value must be between 1 and 256 | APP_RUNTIME_TMPFS_MAX | yes | Most tmpfs mounts one service may declare, from 1 to 256. A change applies to the next deploy or runtime edit; running containers keep their options until recreated. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set runtime.tmpfs_max | Settings > Runtime, Deploys card |
runtime.tmpfs_max_bytes | int | 1073741824 | value must be between 1048576 and 68719476736 | APP_RUNTIME_TMPFS_MAX_BYTES | yes | Largest size in bytes of one tmpfs mount, from 1 MiB to 64 GiB. A change applies to the next deploy or runtime edit; running containers keep their options until recreated. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set runtime.tmpfs_max_bytes | Settings > Runtime, Deploys card |
runtime.ulimit_bytes_max | int | 1073741824 | value must be between 1 and 1099511627776 | APP_RUNTIME_ULIMIT_BYTES_MAX | yes | Largest value in bytes for a size ulimit (core, stack, memlock, fsize), from 1 to 1 TiB. A change applies to the next deploy or runtime edit; running containers keep their options until recreated. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set runtime.ulimit_bytes_max | Settings > Runtime, Deploys card |
runtime.ulimit_count_max | int | 4194304 | value must be between 1 and 1073741824 | APP_RUNTIME_ULIMIT_COUNT_MAX | yes | Largest value for a counting ulimit (nofile, nproc, cpu), from 1 to 1073741824. A change applies to the next deploy or runtime edit; running containers keep their options until recreated. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set runtime.ulimit_count_max | Settings > Runtime, Deploys card |
stacks.history_limit | int | 50 | value must be between 1 and 1000 | APP_STACK_HISTORY_LIMIT | yes | Most stack revisions listed per stack. From 1 to 1000. The next request uses a changed value. | levelrail-cli settings runtime get|set stacks.history_limit | Settings > Runtime, Deploys card |
tags.max_per_app | int | 20 | value must be between 1 and 500 | APP_MAX_TAGS_PER_APP | yes | Most tags one app may carry. From 1 to 500. Tags already attached are kept when the value is lowered. | levelrail-cli settings runtime get|set tags.max_per_app | Settings > Runtime, Deploys card |
tags.max_per_resource | int | 20 | value must be between 1 and 500 | APP_MAX_TAGS_PER_RESOURCE | yes | Most tags one database, node, domain, bucket or network may carry. From 1 to 500. A resource already over the cap keeps its tags but cannot gain more. | levelrail-cli settings runtime get|set tags.max_per_resource | Settings > Runtime, Deploys card |
upgrade.verify_backup | bool | true | any valid bool | none | yes | Before an upgrade goes on, restore the fresh control plane backup into a temporary copy, check it and delete the copy. A backup that does not restore refuses the upgrade. The check only reads the backup and never touches the live data. It is skipped with a warning when free disk space is short. | levelrail-cli settings runtime get|set upgrade.verify_backup | Settings > Runtime, Deploys card |
views.filter_max_keys | int | 12 | value must be between 1 and 32 | APP_SAVED_VIEW_FILTER_MAX_KEYS | yes | Most filter fields one saved list view may store. From 1 to 32. | levelrail-cli settings runtime get|set views.filter_max_keys | Settings > Runtime, Deploys card |
views.filter_value_max_bytes | int | 512 | value must be between 16 and 4096 | APP_SAVED_VIEW_FILTER_VALUE_MAX_BYTES | yes | Most bytes in one filter value of a saved list view. From 16 to 4096. | levelrail-cli settings runtime get|set views.filter_value_max_bytes | Settings > Runtime, Deploys card |
views.max_per_user | int | 100 | value must be between 1 and 1000 | APP_SAVED_VIEW_MAX_PER_USER | yes | Most saved list views one user or token may keep. From 1 to 1000. Existing views are kept when the value is lowered. | levelrail-cli settings runtime get|set views.max_per_user | Settings > Runtime, Deploys card |
views.name_max_chars | int | 64 | value must be between 1 and 200 | APP_SAVED_VIEW_NAME_MAX_CHARS | yes | Most characters in the name of a saved list view. From 1 to 200. | levelrail-cli settings runtime get|set views.name_max_chars | Settings > Runtime, Deploys card |
volumes.import_overwrite | bool | false | any valid bool | APP_VOLUMES_IMPORT_OVERWRITE | yes | When on, an import with the overwrite flag may replace a volume that already holds files. Off by default: imports only fill an empty volume. Take a backup first when you turn it on. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set volumes.import_overwrite | Settings > Runtime, Deploys card |
volumes.transfer_max_bytes | int | 10737418240 | value must be between 1048576 and 4398046511104 | APP_VOLUMES_TRANSFER_MAX_BYTES | yes | Largest volume archive in bytes that an export may produce or an import may unpack; a bigger transfer stops with HTTP 413. Between 1 MiB and 4 TiB. A change applies to the next transfer. | levelrail-cli settings runtime get|set volumes.transfer_max_bytes | Settings > Runtime, Deploys card |
volumes.transfer_max_concurrent | int | 1 | value must be between 1 and 16 | APP_VOLUMES_TRANSFER_MAX_CONCURRENT | yes | How many volume imports this control plane stages at once, from 1 to 16. A further import is refused with HTTP 429 until one finishes. A change applies to the next import. | levelrail-cli settings runtime get|set volumes.transfer_max_concurrent | Settings > Runtime, Deploys card |
volumes.transfer_spool_dir | string | volume-transfer | any valid string | APP_VOLUMES_TRANSFER_SPOOL_DIR | yes | Folder name under the data directory where an import archive is staged while it is checked. A plain name, no slashes. Leftover files in it are removed when the control plane starts. A change applies to the next import. | levelrail-cli settings runtime get|set volumes.transfer_spool_dir | Settings > Runtime, Deploys card |
volumes.transfer_timeout | duration | 30m | value must be a duration between 1m0s and 24h0m0s | APP_VOLUMES_TRANSFER_TIMEOUT | yes | How long one volume export or import may run before it is cancelled, from 1m to 24h. A change applies to the next transfer. | levelrail-cli settings runtime get|set volumes.transfer_timeout | Settings > Runtime, Deploys card |
Observability
| Key | Type | Default | Range | Env seed | Live | Description | CLI | Dashboard |
|---|---|---|---|---|---|---|---|---|
api.apps_metrics_max | int | 200 | value must be between 1 and 5000 | APP_APPS_METRICS_MAX | yes | Most apps one batch metrics request returns; the rest are left out. From 1 to 5000. The next request uses a changed value. | levelrail-cli settings runtime get|set api.apps_metrics_max | Settings > Runtime, Observability card |
api.expensive_read_ttl | int | 0 | value must be between 0 and 3600 | LEVELRAIL_EXPENSIVE_READ_TTL_SECONDS | yes | Seconds the API reuses the answer of costly read endpoints. 0 uses the built-in default. | levelrail-cli settings runtime get|set api.expensive_read_ttl | Settings > Runtime, Observability card |
app_metrics.max_body_bytes | int | 1048576 | value must be between 4096 and 16777216 | APP_APP_METRICS_MAX_BODY_BYTES | yes | Largest metrics response read, in bytes, from 4096 to 16777216; a larger body fails the scrape and nothing is stored. | levelrail-cli settings runtime get|set app_metrics.max_body_bytes | Settings > Runtime, Observability card |
app_metrics.max_label_bytes | int | 65536 | value must be between 1024 and 1048576 | APP_APP_METRICS_MAX_LABEL_BYTES | yes | Most label text kept from one scrape, in bytes, from 1024 to 1048576; series past it are dropped and counted. | levelrail-cli settings runtime get|set app_metrics.max_label_bytes | Settings > Runtime, Observability card |
app_metrics.max_labels | int | 10 | value must be between 1 and 30 | APP_APP_METRICS_MAX_LABELS | yes | Most labels one series may carry, from 1 to 30; a series with more is dropped to keep cardinality bounded. | levelrail-cli settings runtime get|set app_metrics.max_labels | Settings > Runtime, Observability card |
app_metrics.max_series | int | 500 | value must be between 10 and 10000 | APP_APP_METRICS_MAX_SERIES | yes | Most distinct series stored per app per scrape, from 10 to 10000; the rest are dropped and counted. | levelrail-cli settings runtime get|set app_metrics.max_series | Settings > Runtime, Observability card |
app_metrics.max_stored_rows | int | 500000 | value must be between 1000 and 10000000 | APP_APP_METRICS_MAX_STORED_ROWS | yes | Most samples stored per app, from 1000 to 10000000; at the limit new scrapes are dropped until retention frees room. | levelrail-cli settings runtime get|set app_metrics.max_stored_rows | Settings > Runtime, Observability card |
app_metrics.query_max_points | int | 10000 | value must be between 100 and 100000 | APP_APP_METRICS_QUERY_MAX_POINTS | yes | Most stored samples one scraped metrics query returns, from 100 to 100000, so a wide window cannot load the whole table. | levelrail-cli settings runtime get|set app_metrics.query_max_points | Settings > Runtime, Observability card |
app_metrics.retention_hours | int | 72 | value must be between 1 and 720 | APP_APP_METRICS_RETENTION_HOURS | yes | Hours of scraped app samples kept, from 1 to 720; older samples are deleted on the next scrape tick. | levelrail-cli settings runtime get|set app_metrics.retention_hours | Settings > Runtime, Observability card |
app_metrics.scrape_interval | duration | 60s | value must be a duration between 15s and 1h0m0s | APP_APP_METRICS_SCRAPE_INTERVAL | yes | How often the control plane reads each app’s own metrics endpoint, from 15s to 1h. The next tick uses a changed value. | levelrail-cli settings runtime get|set app_metrics.scrape_interval | Settings > Runtime, Observability card |
app_metrics.scrape_timeout | duration | 5s | value must be a duration between 1s and 30s | APP_APP_METRICS_SCRAPE_TIMEOUT | yes | How long one scrape may take, from 1s to 30s, including connect and body read. | levelrail-cli settings runtime get|set app_metrics.scrape_timeout | Settings > Runtime, Observability card |
app_metrics.scrape_workers | int | 4 | value must be between 1 and 16 | APP_APP_METRICS_SCRAPE_WORKERS | yes | How many apps are scraped at once, from 1 to 16, so one slow endpoint cannot delay the others. | levelrail-cli settings runtime get|set app_metrics.scrape_workers | Settings > Runtime, Observability card |
apps.containers_inspect_timeout | duration | 5s | value must be a duration between 1s and 2m0s | APP_CONTAINERS_INSPECT_TIMEOUT | yes | How long the app containers view waits for a node’s live inspect (health, restarts, networks, mounts), from 1s to 2m. When it runs out the view still answers, with those fields marked unavailable. The next request uses a changed value. | levelrail-cli settings runtime get|set apps.containers_inspect_timeout | Settings > Runtime, Observability card |
autoscale.gauge_max_bytes | int | 1048576 | value must be between 1024 and 67108864 | APP_AUTOSCALE_GAUGE_MAX_BYTES | yes | The most bytes read from an app’s gauge endpoint per scrape, from 1024 to 67108864; a larger response is cut off and the reading counts as unknown. | levelrail-cli settings runtime get|set autoscale.gauge_max_bytes | Settings > Runtime, Observability card |
autoscale.gauge_timeout | duration | 3s | value must be a duration between 500ms and 1m0s | APP_AUTOSCALE_GAUGE_TIMEOUT | yes | How long one scrape of an app’s gauge endpoint may take, from 500ms to 1m; the next autoscale evaluation uses a changed value. | levelrail-cli settings runtime get|set autoscale.gauge_timeout | Settings > Runtime, Observability card |
database_viewer.max_bytes | int | 4194304 | value must be between 1024 and 1073741824 | APP_DB_QUERY_MAX_BYTES | yes | Total result size one console query may return. | levelrail-cli settings runtime get|set database_viewer.max_bytes | Settings > Runtime, Observability card |
database_viewer.max_cell_bytes | int | 65536 | value must be between 64 and 16777216 | APP_DB_QUERY_MAX_CELL_BYTES | yes | Largest single cell shown before it is cut off. | levelrail-cli settings runtime get|set database_viewer.max_cell_bytes | Settings > Runtime, Observability card |
database_viewer.max_rows | int | 1000 | value must be between 1 and 10000000 | APP_DB_QUERY_MAX_ROWS | yes | Rows one console query may return, from 1 to 10000000. | levelrail-cli settings runtime get|set database_viewer.max_rows | Settings > Runtime, Observability card |
database_viewer.max_sql_bytes | int | 65536 | value must be between 256 and 16777216 | APP_DB_QUERY_MAX_SQL_BYTES | yes | Largest SQL text the console and saved queries accept. | levelrail-cli settings runtime get|set database_viewer.max_sql_bytes | Settings > Runtime, Observability card |
database_viewer.query_timeout | duration | 15s | value must be a duration between 1s and 10m0s | APP_DB_QUERY_TIMEOUT | yes | How long one console query may run before it is cancelled, from 1s to 10m. | levelrail-cli settings runtime get|set database_viewer.query_timeout | Settings > Runtime, Observability card |
database_viewer.schema_max_rows | int | 5000 | value must be between 1 and 10000000 | APP_DB_SCHEMA_MAX_ROWS | yes | Tables listed by the schema browser. | levelrail-cli settings runtime get|set database_viewer.schema_max_rows | Settings > Runtime, Observability card |
db.compact_min_free_percent | int | 10 | value must be between 0 and 100 | APP_DB_COMPACT_MIN_FREE_PERCENT | yes | Percent of free pages below which a compaction request is declined unless forced. From 0 to 100. Compaction only ever runs on request. | levelrail-cli settings runtime get|set db.compact_min_free_percent | Settings > Runtime, Observability card |
db.space_report_rows | int | 20 | value must be between 1 and 200 | APP_DB_SPACE_REPORT_ROWS | yes | Most tables the database space report lists, largest first. From 1 to 200. The next request uses a changed value. | levelrail-cli settings runtime get|set db.space_report_rows | Settings > Runtime, Observability card |
deploy.explain_log_lines | int | 8 | value must be between 1 and 200 | APP_DEPLOY_EXPLAIN_LOG_LINES | yes | How many trailing log lines the failed-deploy explanation quotes, from 1 to 200. The next explanation uses a changed value. | levelrail-cli settings runtime get|set deploy.explain_log_lines | Settings > Runtime, Observability card |
disk.critical_free_mb | int | 512 | value must be between 16 and 1048576 MiB (0.016 to 1024 GB on the Storage page) | APP_DISK_CRITICAL_FREE_MB | yes | Free space in MiB below which builds, image pulls and backups are refused and the disk reserve is released (16 to 1048576). A value above the low threshold is treated as equal to it. | levelrail-cli settings runtime get|set disk.critical_free_mb | Settings > Runtime, Observability card |
disk.forecast_min_days | int | 7 | value must be between 2 and 30 | APP_DISK_FORECAST_MIN_DAYS | yes | Distinct days of samples required before a days-until-full number is shown, from 2 to 30, so the estimate is never a guess from a few points. | levelrail-cli settings runtime get|set disk.forecast_min_days | Settings > Runtime, Observability card |
disk.forecast_window_days | int | 30 | value must be between 7 and 365 | APP_DISK_FORECAST_WINDOW_DAYS | yes | Days of recent samples the days-until-full forecast fits, from 7 to 365; a longer window smooths spikes and reacts slower. The next history request uses a changed value. | levelrail-cli settings runtime get|set disk.forecast_window_days | Settings > Runtime, Observability card |
disk.history_retention_days | int | 90 | value must be between 7 and 730 | APP_DISK_HISTORY_RETENTION_DAYS | yes | Days of daily disk samples kept for the storage trend and forecast, from 7 to 730; older samples are deleted on the next sampler tick. | levelrail-cli settings runtime get|set disk.history_retention_days | Settings > Runtime, Observability card |
disk.history_sample_interval | duration | 24h | value must be a duration between 1h0m0s and 168h0m0s | APP_DISK_HISTORY_SAMPLE_INTERVAL | yes | How often the control plane records free space and per-category usage for the storage trend, from 1h to 168h; a sample is also taken at boot when the last one is older than this. | levelrail-cli settings runtime get|set disk.history_sample_interval | Settings > Runtime, Observability card |
disk.low_free_mb | int | 1024 | value must be between 64 and 1048576 MiB (0.062 to 1024 GB on the Storage page) | APP_DISK_LOW_FREE_MB | yes | Free space in MiB on the data or Docker volume below which the disk guard raises a low-disk warning and alert (64 to 1048576). Critical is clamped to this value when it is higher. | levelrail-cli settings runtime get|set disk.low_free_mb | Settings > Runtime, Observability card |
disk.reserve_mb | int | 16 | value must be between 0 and 4096 | APP_DISK_RESERVE_MB | yes | Size in MiB of the placeholder file kept in the data dir so SQLite can still commit when the disk fills; it is released below the critical threshold (0 to 4096, 0 turns the reserve off). | levelrail-cli settings runtime get|set disk.reserve_mb | Settings > Runtime, Observability card |
events.changes_buffer | int | 64 | value must be between 8 and 1024 | APP_CHANGES_STREAM_BUFFER | yes | Queued change nudges per open stream before new ones are coalesced. From 8 to 1024. Applies to streams opened after the change. | levelrail-cli settings runtime get|set events.changes_buffer | Settings > Runtime, Observability card |
events.changes_heartbeat | duration | 20s | value must be a duration between 5s and 5m0s | APP_CHANGES_STREAM_HEARTBEAT | yes | How often an idle change stream sends a keepalive and re-reads the caller’s access, from 5s to 5m. | levelrail-cli settings runtime get|set events.changes_heartbeat | Settings > Runtime, Observability card |
events.changes_max_streams_per_caller | int | 4 | value must be between 1 and 32 | APP_CHANGES_STREAM_MAX_PER_CALLER | yes | Most live change streams one user or token may hold open at once. From 1 to 32. Extra connections get 429. | levelrail-cli settings runtime get|set events.changes_max_streams_per_caller | Settings > Runtime, Observability card |
footprint.gc_percent | int | 50 | value must be between 10 and 400 | APP_GC_PERCENT | yes | How far the heap may grow past live data before a collection, from 10 to 400 percent. Lower uses less memory and a little more CPU. Re-read every 30 seconds. Ignored while the GOGC environment variable is set. | levelrail-cli settings runtime get|set footprint.gc_percent | Settings > Runtime, Observability card |
footprint.memlimit_percent | int | 80 | value must be between 0 and 95 | APP_GOMEMLIMIT_PERCENT | yes | Percent of container or host memory the Go runtime tries to stay under, from 0 to 95; 0 lifts the limit. Re-read every 30 seconds. Ignored while the GOMEMLIMIT environment variable is set. | levelrail-cli settings runtime get|set footprint.memlimit_percent | Settings > Runtime, Observability card |
footprint.trim_interval | duration | 2m0s | value must be a duration between 30s and 24h0m0s | APP_MEM_TRIM_INTERVAL | yes | How often idle heap is handed back to the operating system, from 30 seconds to 24 hours. Re-read every 30 seconds. | levelrail-cli settings runtime get|set footprint.trim_interval | Settings > Runtime, Observability card |
footprint.trim_min_idle_mb | int | 24 | value must be between 0 and 4096 | APP_MEM_TRIM_MIN_IDLE_MB | yes | Idle heap in MiB that must build up before a trim runs, from 0 to 4096. Re-read every 30 seconds. | levelrail-cli settings runtime get|set footprint.trim_min_idle_mb | Settings > Runtime, Observability card |
heartbeat.job_backoff_base | duration | 2s | any valid duration | APP_HEARTBEAT_JOB_BACKOFF_BASE | yes | First wait before retrying a failed job ping; it doubles on each retry up to the maximum. | levelrail-cli settings runtime get|set heartbeat.job_backoff_base | Settings > Runtime, Observability card |
heartbeat.job_backoff_max | duration | 30s | any valid duration | APP_HEARTBEAT_JOB_BACKOFF_MAX | yes | Upper bound on the wait between job ping retries. | levelrail-cli settings runtime get|set heartbeat.job_backoff_max | Settings > Runtime, Observability card |
heartbeat.job_max_attempts | int | 3 | value must be between 1 and 20 | APP_HEARTBEAT_JOB_MAX_ATTEMPTS | yes | How many times a per-job heartbeat ping is tried before it is given up. | levelrail-cli settings runtime get|set heartbeat.job_max_attempts | Settings > Runtime, Observability card |
heartbeat.job_queue | int | 64 | value must be between 1 and 10000 | APP_HEARTBEAT_JOB_QUEUE | yes | How many job pings may wait to be sent before new ones are dropped. A change applies at once. | levelrail-cli settings runtime get|set heartbeat.job_queue | Settings > Runtime, Observability card |
incidents.postmortem_action_items_max | int | 50 | value must be between 1 and 500 | APP_INCIDENT_POSTMORTEM_ACTION_ITEMS_MAX | yes | Action items one postmortem may list, from 1 to 500. | levelrail-cli settings runtime get|set incidents.postmortem_action_items_max | Settings > Runtime, Observability card |
incidents.postmortem_body_max | int | 1048576 | value must be between 65536 and 16777216 | APP_INCIDENT_POSTMORTEM_BODY_MAX | yes | Largest postmortem edit request read, from 65536 to 16777216 bytes, whatever the field limits add up to. | levelrail-cli settings runtime get|set incidents.postmortem_body_max | Settings > Runtime, Observability card |
incidents.postmortem_field_max | int | 8000 | value must be between 256 and 65536 | APP_INCIDENT_POSTMORTEM_FIELD_MAX | yes | Longest summary, impact, root cause, resolution or single action item accepted, from 256 to 65536 bytes. | levelrail-cli settings runtime get|set incidents.postmortem_field_max | Settings > Runtime, Observability card |
log_rules.eval_interval | duration | 1m | value must be a duration between 1s and 24h0m0s | APP_LOG_RULE_EVAL_INTERVAL | yes | How often each log rule runs, from 1s to 24h. | levelrail-cli settings runtime get|set log_rules.eval_interval | Settings > Runtime, Observability card |
log_rules.max_rows | int | 5000 | value must be between 1 and 1000000 | APP_LOG_RULE_MAX_ROWS | yes | Log rows one rule evaluation may read. | levelrail-cli settings runtime get|set log_rules.max_rows | Settings > Runtime, Observability card |
log_rules.max_window | duration | 1h | value must be a duration between 1m0s and 720h0m0s | APP_LOG_RULE_MAX_WINDOW | yes | Longest window a log rule may look back over, from 1m to 720h. | levelrail-cli settings runtime get|set log_rules.max_window | Settings > Runtime, Observability card |
log_rules.samples | int | 5 | value must be between 0 and 100 | APP_LOG_RULE_SAMPLES | yes | Matching lines attached to a firing alert. | levelrail-cli settings runtime get|set log_rules.samples | Settings > Runtime, Observability card |
logs.export_max_lines | int | 5000 | value must be between 100 and 1000000 | APP_LOG_EXPORT_MAX_LINES | yes | Most log lines one log download returns, newest kept. From 100 to 1000000. The next download uses a changed value. | levelrail-cli settings runtime get|set logs.export_max_lines | Settings > Runtime, Observability card |
metrics.idle_interval | duration | 1m | value must be a duration between 15s and 24h0m0s | APP_METRICS_IDLE_INTERVAL | no, restart | How often metrics are collected while nobody has a dashboard open, from 15 seconds to 24 hours. Takes effect after a restart. | levelrail-cli settings runtime get|set metrics.idle_interval | Settings > Runtime, Observability card |
metrics.presence_window | duration | 2m | value must be a duration between 15s and 24h0m0s | APP_METRICS_PRESENCE_WINDOW | no, restart | How long after the last metrics read a viewer still counts as watching, from 15 seconds to 24 hours. Takes effect after a restart. | levelrail-cli settings runtime get|set metrics.presence_window | Settings > Runtime, Observability card |
monitors.raw_retention | duration | 48h | value must be a duration between 1h0m0s and 8760h0m0s | APP_MONITOR_RAW_RETENTION | yes | How long each uptime monitor check result is kept before the prune job deletes it, from 1h to 8760h; hourly rollups are kept on their own window. | levelrail-cli settings runtime get|set monitors.raw_retention | Settings > Runtime, Observability card |
nodes.alert_cpu_percent | int | 85 | value must be between 1 and 100 | APP_ALERT_NODE_CPU_PERCENT | yes | Summed CPU percent of the services on a node that a node_cpu rule treats as pressure, from 1 to 100. A node can override it. | levelrail-cli settings runtime get|set nodes.alert_cpu_percent | Settings > Runtime, Observability card |
nodes.alert_disk_percent | int | 90 | value must be between 1 and 100 | APP_ALERT_NODE_DISK_SPACE_THRESHOLD_PERCENT | yes | Used disk percent that a node_disk_space rule fires at, from 1 to 100. A node can override it. | levelrail-cli settings runtime get|set nodes.alert_disk_percent | Settings > Runtime, Observability card |
nodes.alert_memory_percent | int | 90 | value must be between 1 and 100 | APP_ALERT_NODE_MEMORY_PERCENT | yes | Used host memory percent that a node_memory rule treats as pressure, from 1 to 100. A node can override it. | levelrail-cli settings runtime get|set nodes.alert_memory_percent | Settings > Runtime, Observability card |
nodes.alert_sustained_intervals | int | 3 | value must be between 1 and 60 | APP_ALERT_NODE_SUSTAINED_INTERVALS | yes | Consecutive alert evaluations a node must stay over its CPU or memory threshold before node_cpu or node_memory fires, from 1 to 60, so one spike does not page. | levelrail-cli settings runtime get|set nodes.alert_sustained_intervals | Settings > Runtime, Observability card |
nodes.patch_output_tail_lines | int | 200 | value must be between 10 and 5000 | APP_NODES_PATCH_OUTPUT_TAIL_LINES | yes | How many trailing lines of package manager output each patch run keeps, with secret looking values masked. | levelrail-cli settings runtime get|set nodes.patch_output_tail_lines | Settings > Runtime, Observability card |
nodes.patch_poll_interval | duration | 2s | value must be a duration between 1s and 1m0s | APP_NODES_PATCH_POLL_INTERVAL | yes | How often the control plane reads the state of a package upgrade running as its own systemd unit. Clamped to 500ms through 60s. | levelrail-cli settings runtime get|set nodes.patch_poll_interval | Settings > Runtime, Observability card |
observability.metrics_scrape_enabled | bool | true | any valid bool | APP_METRICS_SCRAPE_ENABLED | yes | Serve GET /metrics to callers holding a read token. Turn off to answer 404 without revoking tokens. | levelrail-cli settings runtime get|set observability.metrics_scrape_enabled | Settings > Runtime, Observability card |
perf.slow_statement_ms | int | 100 | value must be between 1 and 60000 | APP_PERF_SLOW_STATEMENT_MS | yes | A statement at or above this many milliseconds is logged (statement text only, never values) and kept in the slowest statements list, from 1 to 60000. | levelrail-cli settings runtime get|set perf.slow_statement_ms | Settings > Runtime, Observability card |
perf.slow_statement_ring | int | 20 | value must be between 1 and 500 | APP_PERF_SLOW_STATEMENT_RING | yes | How many distinct slow statements the control plane remembers, from 1 to 500. | levelrail-cli settings runtime get|set perf.slow_statement_ring | Settings > Runtime, Observability card |
perf.statement_timing | bool | false | any valid bool | APP_PERF_STATEMENT_TIMING | yes | Time every statement the control plane runs against its own database, count them per request, send a Server-Timing header to admins and keep the slowest statements. Off costs nothing. The next request uses a changed value. | levelrail-cli settings runtime get|set perf.statement_timing | Settings > Runtime, Observability card |
reconcile.resync_seconds | int | 30 | value must be between 5 and 3600 | APP_RECONCILE_RESYNC_SECONDS | yes | Seconds between full reconcile passes that catch any event the stream missed. From 5 to 3600. Takes effect at the next resync tick. | levelrail-cli settings runtime get|set reconcile.resync_seconds | Settings > Runtime, Observability card |
storage.critical_free_percent | int | 5 | value must be between 1 and 25 | APP_STORAGE_CRITICAL_FREE_PERCENT | yes | Free space percent below which the Storage page reads the disk as critical, from 1 to 25; keep it below the low percent, a value at or above it is treated as just under it. | levelrail-cli settings runtime get|set storage.critical_free_percent | Settings > Runtime, Observability card |
storage.large_unmanaged_image_mb | int | 500 | value must be between 1 and 1048576 | APP_STORAGE_LARGE_UNMANAGED_IMAGE_MB | yes | Size in MiB at which the Storage page flags an image that no app owns as large, from 1 to 1048576; the page reads the new value on its next refresh. | levelrail-cli settings runtime get|set storage.large_unmanaged_image_mb | Settings > Runtime, Observability card |
storage.low_free_percent | int | 15 | value must be between 2 and 50 | APP_STORAGE_LOW_FREE_PERCENT | yes | Free space percent below which the Storage page reads the disk as low when the MiB floors are unavailable, from 2 to 50; the page reads the new value on its next refresh. | levelrail-cli settings runtime get|set storage.low_free_percent | Settings > Runtime, Observability card |
store.cache_size_mb | int | 0 | value must be between 0 and 4096 | APP_DB_CACHE_SIZE_MB | yes | Page cache per control plane database connection in megabytes, 0 to 4096. 0 keeps the SQLite default. Applies to the writer and read connections within a minute. | levelrail-cli settings runtime get|set store.cache_size_mb | Settings > Runtime, Observability card |
store.mmap_size_mb | int | 0 | value must be between 0 and 16384 | APP_DB_MMAP_SIZE_MB | yes | How much of the control plane database file SQLite may memory map, 0 to 16384. 0 turns memory mapping off. Applies within a minute. | levelrail-cli settings runtime get|set store.mmap_size_mb | Settings > Runtime, Observability card |
store.optimize_interval | duration | 6h | value must be 0 or a duration up to 720h0m0s | APP_DB_OPTIMIZE_INTERVAL | yes | How often the control plane database refreshes its query planner statistics (PRAGMA optimize). 0 turns the periodic run off; one run still happens at shutdown. A saved change applies within a minute. | levelrail-cli settings runtime get|set store.optimize_interval | Settings > Runtime, Observability card |
store.read_connections | int | 4 | value must be between 1 and 32 | APP_DB_READ_CONNS | yes | How many read-only connections the control plane database keeps, from 1 to 32. A saved change resizes the pool within a minute. Turning the pool off (APP_DB_READ_CONNS=0) stays a boot-only environment choice and is not changed live. | levelrail-cli settings runtime get|set store.read_connections | Settings > Runtime, Observability card |
store.synchronous | string | default | one of default, normal, full | APP_DB_SYNCHRONOUS | yes | How hard SQLite syncs the WAL to disk: default, normal or full. Normal is faster but a power loss can drop the last commits. OFF is not offered. Applies within a minute. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set store.synchronous | Settings > Runtime, Observability card |
store.temp_store | string | default | one of default, file, memory | APP_DB_TEMP_STORE | yes | Where SQLite keeps temporary tables and indexes: default, file or memory. Memory is faster but uses RAM on large sorts. Applies within a minute. | levelrail-cli settings runtime get|set store.temp_store | Settings > Runtime, Observability card |
store.touch_flush_interval | duration | 5s | value must be a duration between 0s and 1h0m0s | LEVELRAIL_TOUCH_FLUSH_INTERVAL | no, restart | How often buffered last-seen and last-used timestamps are written, up to 1 hour. 0 writes through on every request. Takes effect after a restart. | levelrail-cli settings runtime get|set store.touch_flush_interval | Settings > Runtime, Observability card |
system.processes_max_rows | int | 25 | value must be between 1 and 500 | APP_SYSTEM_PROCESSES_MAX_ROWS | yes | Most processes the control plane host process table lists, largest memory first. From 1 to 500. The next request uses a changed value. | levelrail-cli settings runtime get|set system.processes_max_rows | Settings > Runtime, Observability card |
telemetry.access_log_retention | duration | 8760h0m0s | value must be a duration between 1h0m0s and 8760h0m0s | APP_ACCESS_LOG_RETENTION | yes | How long the recent-requests view keeps a request, from 1h to 8760h; the ring still holds only the latest entries per route. The next read uses a changed value. An environment value of 0 now means the maximum. | levelrail-cli settings runtime get|set telemetry.access_log_retention | Settings > Runtime, Observability card |
telemetry.access_log_size | int | 1000 | value must be between 0 and 100000 | APP_ACCESS_LOG_SIZE | yes | How many recent requests the edge keeps in memory per route, from 0 to 100000; 0 turns recording off. Memory is bounded by routes times this size. A saved change resizes the rings within a second, keeping the newest entries, and 0 frees them. | levelrail-cli settings runtime get|set telemetry.access_log_size | Settings > Runtime, Observability card |
telemetry.access_search_max_concurrent | int | 4 | value must be between 1 and 32 | APP_ACCESS_SEARCH_MAX_CONCURRENT | yes | Searches that may run at once on this control plane, from 1 to 32; more answer 429. | levelrail-cli settings runtime get|set telemetry.access_search_max_concurrent | Settings > Runtime, Observability card |
telemetry.access_search_max_rows | int | 200 | value must be between 1 and 5000 | APP_ACCESS_SEARCH_MAX_ROWS | yes | Rows one access log search page may return, from 1 to 5000; larger requests are clamped. | levelrail-cli settings runtime get|set telemetry.access_search_max_rows | Settings > Runtime, Observability card |
telemetry.access_search_max_scan | int | 200000 | value must be between 1000 and 10000000 | APP_ACCESS_SEARCH_MAX_SCAN | yes | Records one search may examine before it stops and reports a partial result, from 1000 to 10000000. | levelrail-cli settings runtime get|set telemetry.access_search_max_scan | Settings > Runtime, Observability card |
telemetry.access_search_max_term | int | 256 | value must be between 1 and 4096 | APP_ACCESS_SEARCH_MAX_TERM | yes | Longest path prefix or search text accepted, from 1 to 4096 bytes. | levelrail-cli settings runtime get|set telemetry.access_search_max_term | Settings > Runtime, Observability card |
telemetry.access_search_max_window | duration | 24h | value must be a duration between 1m0s and 720h0m0s | APP_ACCESS_SEARCH_MAX_WINDOW | yes | Longest time range one access log search may cover, from 1m to 720h. Rows older than the in-memory log keeps are gone either way. | levelrail-cli settings runtime get|set telemetry.access_search_max_window | Settings > Runtime, Observability card |
telemetry.log_budget_mb | int | 0 | value must be 0 (unlimited) or between 16 and 10485760 MiB | APP_LOG_BUDGET_MB | yes | Stored log size in MiB each app may use before the sweep trims its oldest lines; 0 means unlimited, otherwise 16 to 10485760. A per-app budget overrides it. | levelrail-cli settings runtime get|set telemetry.log_budget_mb | Settings > Runtime, Observability card |
telemetry.logs_retention | duration | 360h | value must be a duration between 1h0m0s and 8760h0m0s | APP_LOGS_RETENTION | yes | How long stored app logs, traces and error events are kept before the hourly sweep deletes them, from 1h to 8760h; the next sweep uses a changed value. | levelrail-cli settings runtime get|set telemetry.logs_retention | Settings > Runtime, Observability card |
telemetry.metrics_retention | duration | 360h | value must be a duration between 1h0m0s and 8760h0m0s | APP_METRICS_RETENTION | yes | How long raw container metric samples are kept before the prune job deletes them, from 1h to 8760h; older data stays available in the coarser rollup tiers. | levelrail-cli settings runtime get|set telemetry.metrics_retention | Settings > Runtime, Observability card |
telemetry.visitor_history_retention | duration | 168h0m0s | value must be 0 (off) or a duration between 1h0m0s and 2160h0m0s | APP_VISITOR_HISTORY_RETENTION | yes | How long hourly visitor rollups (requests, status classes, unique visitors per salt period, a few top pages and referrers) are kept per app and domain so the 7d and 30d visitor windows survive a restart, from 1h to 2160h; 0 keeps nothing beyond the in-memory log. No client address is ever stored. A saved change applies at the next flush and 0 removes the stored rollups. | levelrail-cli settings runtime get|set telemetry.visitor_history_retention | Settings > Runtime, Observability card |
telemetry.visitor_salt_rotation | duration | 24h0m0s | value must be a duration between 1h0m0s and 720h0m0s | APP_VISITOR_SALT_ROTATION | yes | How often the salt used to hash client addresses for the visitor counts changes, from 1h to 720h. Addresses are never stored; the same person is counted once per salt period, so a shorter period is more private and counts a returning visitor more than once. The next read uses a changed value. | levelrail-cli settings runtime get|set telemetry.visitor_salt_rotation | Settings > Runtime, Observability card |
ui.outbound_utm | bool | true | any valid bool | APP_UI_OUTBOUND_UTM | yes | When on, the dashboard adds utm_source, utm_medium and utm_campaign to links that leave for third party sites, such as template homepages, docs and upstream projects, so project maintainers can see where visits come from. Turn it off to send plain links. Only the dashboard reads this value; links are never rewritten on the server. | levelrail-cli settings runtime get|set ui.outbound_utm | Settings > Runtime, Observability card |
vitals.enabled | bool | false | any valid bool | APP_VITALS_ENABLED | yes | Whether a beacon key created by Rotate starts enabled. An app only accepts beacons once it has a saved config with collection on; the Web vitals card switch owns that per app. Read when a key is first created. | levelrail-cli settings runtime get|set vitals.enabled | Settings > Runtime, Observability card |
vitals.flush_interval_seconds | int | 10 | value must be between 1 and 3600 | APP_VITALS_FLUSH_SECONDS | yes | Seconds between writes of buffered web vitals counters, from 1 to 3600. A crash loses at most one interval. | levelrail-cli settings runtime get|set vitals.flush_interval_seconds | Settings > Runtime, Observability card |
vitals.max_body_bytes | int | 4096 | value must be between 256 and 65536 | APP_VITALS_MAX_BODY_BYTES | yes | Largest accepted beacon body in bytes, from 256 to 65536. Bigger bodies answer 413. | levelrail-cli settings runtime get|set vitals.max_body_bytes | Settings > Runtime, Observability card |
vitals.max_routes_per_app | int | 200 | value must be between 1 and 10000 | APP_VITALS_MAX_ROUTES | yes | Distinct routes one app may record per day, from 1 to 10000. Further routes are counted under /other. | levelrail-cli settings runtime get|set vitals.max_routes_per_app | Settings > Runtime, Observability card |
vitals.rate_limit_per_ip_per_minute | int | 120 | value must be between 1 and 1000000 | APP_VITALS_RATE_PER_IP | yes | Beacons accepted per client address per minute, from 1 to 1000000, checked before the body is read. Extra beacons answer 429. | levelrail-cli settings runtime get|set vitals.rate_limit_per_ip_per_minute | Settings > Runtime, Observability card |
vitals.rate_limit_per_minute | int | 600 | value must be between 1 and 1000000 | APP_VITALS_RATE_PER_MIN | yes | Beacons accepted per app per minute, from 1 to 1000000. Extra beacons answer 429 and are dropped. Read on every beacon. | levelrail-cli settings runtime get|set vitals.rate_limit_per_minute | Settings > Runtime, Observability card |
vitals.report_top_routes | int | 50 | value must be between 1 and 500 | APP_VITALS_REPORT_TOP_ROUTES | yes | Busiest routes returned by the Web vitals report and shown on the card, from 1 to 500. | levelrail-cli settings runtime get|set vitals.report_top_routes | Settings > Runtime, Observability card |
volumes.size_history_retention | duration | 168h | value must be a duration between 1h0m0s and 8760h0m0s | APP_VOLUMES_SIZE_HISTORY_RETENTION | yes | How long volume size samples are kept for the size history, from 1h to 8760h. A change applies to the next prune. | levelrail-cli settings runtime get|set volumes.size_history_retention | Settings > Runtime, Observability card |
volumes.usage_alert_percent | int | 90 | value must be between 1 and 100 | APP_VOLUMES_USAGE_ALERT_PERCENT | yes | Percent of a volume’s capacity at which a volume usage rule fires, from 1 to 100. The rule resolves once usage drops below it. A change applies to the next evaluation. | levelrail-cli settings runtime get|set volumes.usage_alert_percent | Settings > Runtime, Observability card |
Data retention
| Key | Type | Default | Range | Env seed | Live | Description | CLI | Dashboard |
|---|---|---|---|---|---|---|---|---|
account.preferences_max_bytes | int | 8192 | value must be between 256 and 65536 | APP_ACCOUNT_PREFERENCES_MAX_BYTES | yes | Largest saved personal preference document (such as appearance synced to your account), from 256 to 65536 bytes. A bigger save is refused with HTTP 413. The next save uses a changed value. | levelrail-cli settings runtime get|set account.preferences_max_bytes | Settings > Runtime, Data retention card |
backup.default_retention_hours | int | 168 | one of 0, 24, 48, 168, 720, 1440, 2160 | APP_BACKUP_DEFAULT_RETENTION_HOURS | yes | Hours a scheduled backup is kept when its database or volume has no count or age rule of its own. The newest backup is never removed. 0 keeps them until a rule or a person deletes them. | levelrail-cli settings runtime get|set backup.default_retention_hours | Settings > Runtime, Data retention card |
backup.hook_max_output_bytes | int | 4096 | value must be between 256 and 65536 | APP_BACKUP_HOOK_MAX_OUTPUT_BYTES | yes | Bytes of a failing hook’s output kept with the backup record, from 256 to 65536, with the command text and known secret shapes masked. The rest is read and discarded. The next hook uses a changed value. | levelrail-cli settings runtime get|set backup.hook_max_output_bytes | Settings > Runtime, Data retention card |
backup.hook_timeout_seconds | int | 60 | value must be between 1 and 600 | APP_BACKUP_HOOK_TIMEOUT_SECONDS | yes | Seconds a volume backup’s pre or post command may run inside the app’s container, from 1 to 600, and never above APP_BACKUP_HOOK_MAX_SECONDS. A pre command that runs longer is killed and the backup is not taken; the post command still runs. The next hook uses a changed value. | levelrail-cli settings runtime get|set backup.hook_timeout_seconds | Settings > Runtime, Data retention card |
backups.compose_restore_timeout | duration | 2h | value must be a duration between 1m0s and 24h0m0s | APP_COMPOSE_RESTORE_TIMEOUT | yes | How long one in-place restore of a compose database may run before it is cancelled, from 1m to 24h. The next restore uses a changed value. | levelrail-cli settings runtime get|set backups.compose_restore_timeout | Settings > Runtime, Data retention card |
backups.drill_interval_hours | int | 168 | value must be between 0 and 8760 | APP_BACKUP_DRILL_INTERVAL_HOURS | yes | Hours between scheduled restore drills of each backed up database or volume, from 0 to 8760. 0 turns scheduled drills off. A drill restores the newest backup into a throwaway target and records a pass or fail. The next scheduler pass uses a changed value. | levelrail-cli settings runtime get|set backups.drill_interval_hours | Settings > Runtime, Data retention card |
backups.drill_retention_days | int | 90 | value must be between 0 and 3650 | APP_BACKUP_DRILL_RETENTION_DAYS | yes | Days of restore drill results to keep, from 0 to 3650. 0 keeps every result. The newest drill of each resource is always kept so health and alerts stay accurate. The next scheduler pass uses a changed value. | levelrail-cli settings runtime get|set backups.drill_retention_days | Settings > Runtime, Data retention card |
backups.drill_timeout | duration | 1h | value must be a duration between 1m0s and 24h0m0s | APP_BACKUP_DRILL_TIMEOUT | yes | How long one scheduled restore drill may run before it is cancelled and recorded as failed, from 1m to 24h. The next drill uses a changed value. | levelrail-cli settings runtime get|set backups.drill_timeout | Settings > Runtime, Data retention card |
backups.schedule_retain_default | int | 0 | value must be between 0 and 1000 | APP_BACKUP_SCHEDULE_RETAIN_DEFAULT | yes | How many backups a compose database schedule keeps when it is saved without a retain count, from 0 to 1000. 0 keeps every backup. Schedules already saved are not changed. | levelrail-cli settings runtime get|set backups.schedule_retain_default | Settings > Runtime, Data retention card |
cdn.purge_history | int | 20 | value must be between 1 and 1000 | APP_CDN_PURGE_HISTORY | yes | How many edge purge records are kept per app in memory, from 1 to 1000. Records reset when the control plane restarts. Applies to the next purge. | levelrail-cli settings runtime get|set cdn.purge_history | Settings > Runtime, Data retention card |
cleanup.enabled | bool | true | any valid bool | APP_CLEANUP_ENABLED | yes | Turn the scheduled cleanup off entirely. Manual cleanups still work. | levelrail-cli settings runtime get|set cleanup.enabled | Settings > Runtime, Data retention card |
cleanup.failing_floor | int | 1 | value must be between 1 and 100 | APP_CLEANUP_FAILING_FLOOR | yes | Failed cleanup runs inside the look-back that fire a cleanup_failing rule whose own threshold is 0, from 1 to 100. | levelrail-cli settings runtime get|set cleanup.failing_floor | Settings > Runtime, Data retention card |
cleanup.failing_window | duration | 24h | value must be a duration between 15m0s and 720h0m0s | APP_CLEANUP_FAILING_WINDOW | yes | How far back the cleanup_failing alert counts failed cleanup runs, from 15m to 720h. A dry run never counts. | levelrail-cli settings runtime get|set cleanup.failing_window | Settings > Runtime, Data retention card |
cleanup.interval | duration | 6h | must be at least 15m0s | APP_CLEANUP_INTERVAL | yes | How often the scheduled cleanup checks every data type. The minimum is 15 minutes. | levelrail-cli settings runtime get|set cleanup.interval | Settings > Runtime, Data retention card |
images.remove_max_per_request | int | 200 | value must be between 1 and 2000 | APP_IMAGES_REMOVE_MAX_PER_REQUEST | yes | Most images one remove request may name or select, from 1 to 2000. Guards against a mistaken select-all. The next request uses a changed value. | levelrail-cli settings runtime get|set images.remove_max_per_request | Settings > Runtime, Data retention card |
nodes.patch_run_history | int | 20 | value must be between 1 and 500 | APP_NODES_PATCH_RUN_HISTORY | yes | How many recent patch runs per node the control plane lists. History lives in memory and resets on restart; the audit log keeps every run. | levelrail-cli settings runtime get|set nodes.patch_run_history | Settings > Runtime, Data retention card |
retention.ai_history_days | int | 90 | one of 0, 30, 60, 90, 180, 365 | APP_RETENTION_AI_HISTORY_DAYS | yes | Days an idle assistant chat and its usage metering are kept. A chat with newer messages is kept whole. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.ai_history_days | Settings > Runtime, Data retention card |
retention.alert_history_days | int | 30 | one of 0, 30, 60, 90, 180, 365 | APP_ALERT_HISTORY_RETENTION | yes | Days an alert history entry is kept. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.alert_history_days | Settings > Runtime, Data retention card |
retention.app_history_days | int | 90 | one of 0, 30, 60, 90, 180, 365 | APP_RETENTION_APP_HISTORY_DAYS | yes | Days app lifecycle events, scheduled deploy history and last canary outcomes are kept. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.app_history_days | Settings > Runtime, Data retention card |
retention.audit_log_days | int | 90 | one of 0, 30, 60, 90, 180, 365; retention cannot be shorter than 90 days, choose 90 or more (or 0 to keep forever) | APP_AUDIT_LOG_RETENTION_DAYS | yes | Days an audit log entry is kept before the cleanup removes it. Sign-in and policy entries follow their own, longer window. 0 keeps everything. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set retention.audit_log_days | Settings > Runtime, Data retention card |
retention.audit_security_days | int | 365 | one of 0, 30, 60, 90, 180, 365; retention cannot be shorter than 365 days, choose 365 or more (or 0 to keep forever) | APP_AUDIT_LOG_SECURITY_RETENTION_DAYS | yes | Days sign-in, step-up, token and policy audit entries are kept. Never shorter than the general window. 0 keeps them forever. Weakening it asks for confirmation. | levelrail-cli settings runtime get|set retention.audit_security_days | Settings > Runtime, Data retention card |
retention.auth_expired_days | int | 30 | one of 0, 30, 60, 90, 180, 365 | APP_RETENTION_AUTH_EXPIRED_DAYS | yes | Days an expired session, device login code or magic link stays stored after it expired. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.auth_expired_days | Settings > Runtime, Data retention card |
retention.email_log_days | int | 30 | one of 0, 30, 60, 90, 180, 365 | APP_EMAIL_LOG_RETENTION_DAYS | yes | Days an email delivery log row is kept. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.email_log_days | Settings > Runtime, Data retention card |
retention.event_webhook_days | int | 30 | one of 0, 30, 60, 90, 180, 365 | APP_EVENT_WEBHOOK_RETENTION | yes | Days a finished outbound event webhook delivery is kept. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.event_webhook_days | Settings > Runtime, Data retention card |
retention.expired_token_days | int | 90 | one of 0, 30, 60, 90, 365 | APP_RETENTION_EXPIRED_TOKEN_DAYS | yes | Days an expired API token stays listed before the cleanup removes it. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.expired_token_days | Settings > Runtime, Data retention card |
retention.probe_attempt_days | int | 90 | one of 0, 30, 60, 90, 180, 365 | APP_RETENTION_PROBE_ATTEMPT_DAYS | yes | Days the per-attempt readiness probe detail of a deploy is kept. 0 keeps it forever. | levelrail-cli settings runtime get|set retention.probe_attempt_days | Settings > Runtime, Data retention card |
retention.restore_history_days | int | 90 | one of 0, 30, 60, 90, 180, 365 | APP_RETENTION_RESTORE_HISTORY_DAYS | yes | Days a finished restore, point-in-time restore or backup drill record is kept. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.restore_history_days | Settings > Runtime, Data retention card |
retention.revoked_token_days | int | 90 | one of 0, 30, 60, 90, 365 | APP_RETENTION_REVOKED_TOKEN_DAYS | yes | Days a revoked API token stays listed before the cleanup removes it. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.revoked_token_days | Settings > Runtime, Data retention card |
retention.status_incident_days | int | 365 | one of 0, 30, 60, 90, 180, 365 | APP_RETENTION_STATUS_INCIDENT_DAYS | yes | Days a resolved incident or completed maintenance stays on the status page record. Open ones are never removed. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.status_incident_days | Settings > Runtime, Data retention card |
retention.usage_cost_days | int | 90 | one of 0, 30, 60, 90, 180, 365 | APP_RETENTION_USAGE_COST_DAYS | yes | Days a daily cost showback snapshot is kept. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.usage_cost_days | Settings > Runtime, Data retention card |
retention.webhook_delivery_days | int | 30 | one of 0, 30, 60, 90, 180, 365 | APP_WEBHOOK_DELIVERY_RETENTION_DAYS | yes | Days a received git webhook delivery is kept for troubleshooting. 0 keeps them forever. | levelrail-cli settings runtime get|set retention.webhook_delivery_days | Settings > Runtime, Data retention card |
scheduled_tasks.history_keep | int | 200 | value must be between 1 and 10000 | APP_JOBS_HISTORY_KEEP | yes | How many recent runs of each scheduled task keep their history (status, exit code, duration, output), at least 1. Older runs are removed after the next run finishes. | levelrail-cli settings runtime get|set scheduled_tasks.history_keep | Settings > Runtime, Data retention card |
scheduled_tasks.max_output_bytes | int | 65536 | value must be between 1024 and 1048576 | APP_JOBS_MAX_OUTPUT_BYTES | yes | How many bytes of output each scheduled task or compose schedule run keeps (the tail, where errors land), between 1024 and 1048576. | levelrail-cli settings runtime get|set scheduled_tasks.max_output_bytes | Settings > Runtime, Data retention card |
spool.max_age_seconds | int | 0 | value must be between 0 and 604800 | LEVELRAIL_SPOOL_MAX_AGE_SECONDS | yes | Seconds an unfinished upload file may sit in the spool before the sweeper removes it. 0 uses the built-in default. | levelrail-cli settings runtime get|set spool.max_age_seconds | Settings > Runtime, Data retention card |
spool.quota_bytes | int | 0 | value must be between 0 and 1099511627776 | LEVELRAIL_SPOOL_QUOTA_BYTES | yes | Most bytes the upload spool may hold. A source zip upload past the cap is refused with 507. 0 uses the built-in default. | levelrail-cli settings runtime get|set spool.quota_bytes | Settings > Runtime, Data retention card |
vitals.retention_days | int | 30 | value must be between 1 and 365 | APP_VITALS_RETENTION_DAYS | yes | Days of web vitals rollups kept, from 1 to 365. Older rows are deleted by a background job every ten minutes. | levelrail-cli settings runtime get|set vitals.retention_days | Settings > Runtime, Data retention card |
Experimental
| Key | Type | Default | Range | Env seed | Live | Description | CLI | Dashboard |
|---|---|---|---|---|---|---|---|---|
onboarding.enabled | bool | true | any valid bool | APP_ONBOARDING_ENABLED | yes | Shows the guided welcome and demo flow to users who have not finished it. Turn it off to hide the flow for every user. Progress is kept, so turning it back on resumes where each user stopped. | levelrail-cli settings runtime get|set onboarding.enabled | Settings > Runtime, Experimental card |
onboarding.restore_reminder_days | int | 7 | value must be between 0 and 365 | APP_ONBOARDING_RESTORE_REMINDER_DAYS | yes | Days after a user starts onboarding before the dashboard reminds them to test a restore, when a backup exists and no restore was ever verified. 0 turns the reminder off. | levelrail-cli settings runtime get|set onboarding.restore_reminder_days | Settings > Runtime, Experimental card |
updates.offered_channels | string_list | stable | colon separated list | APP_UPDATE_CHANNELS_OFFERED | yes | Which release channels the dashboard offers for selection: stable, beta or edge. Others stay valid through the API. An empty list falls back to stable. The next page load shows a changed list. | levelrail-cli settings runtime get|set updates.offered_channels | Settings > Runtime, Experimental card |