Enterprise Deployment Guide

rescile-ee Service Binary

CLI reference for the service-oriented edition binary, including schema validation and module management.

Edit this page on GitHub

rescile-ee Service Binary

rescile-ee is the service-oriented edition of the rescile controller. It is intended to run under systemd or another service manager, produces syslog-style logs, and exposes the same GraphQL, MCP, Vault, and portal endpoints as rescile-ce.

Most global options (--data-dir, --module, --offline, --git-client, etc.) are identical to rescile-ce. The main differences are the output style (no colors, timestamps, severity-aware logging) and the set of exposed commands.

Commands

serve

Builds the graph and starts the GraphQL server, MCP endpoint, Vault server, and portal.

rescile-ee serve --port 7600 --listen 0.0.0.0
  • --init: Run the bootstrap step before serving (copy/merge starter files from loaded modules).

validate

Validates the workspace against central schemas. Output is written to the service log and always includes a summary of the modules, schemas, resources, issue counts, and the final Result: success / Result: failed.

# Use schemas declared in module.toml
rescile-ee validate

# Validate against a specific schema only
rescile-ee validate --schema ./schemas/20260729.schema.json

# Strict validation
rescile-ee validate --schema ./schemas/20260729.schema.json --strict-schemas

# Bootstrap starter files before validating
rescile-ee validate --init
  • --schema: use only the supplied schema source; ignore schemas declared in module.toml.
  • --strict-schemas: treat schema validation warnings as hard errors and validate CSV cell values.
  • --init: run the bootstrap step before validating.

save <FILE>

Builds the graph and writes the raw in-memory representation to a JSON file.

rescile-ee save ./graph.json --init
  • --init: run the bootstrap step before saving.

mod <lock|check|update|fetch|check-schema>

Module dependency management. See Module Dependencies.

rescile-ee mod check-schema --schema ./schemas/20260729.schema.json --strict-schemas

info, license, vault

Information, license display, and vault client commands. These exit immediately without starting a graph build.

Logging

rescile-ee initializes env_logger with syslog-style formatting and disables console colors. Validation findings and build messages are routed through the log crate so they can be captured by journald or any systemd-aware log sink.

Exit codes

  • 0 — command succeeded and validation found no errors.
  • Non-zero — command failure or validation produced errors. Warnings and info notes alone do not cause a non-zero exit unless --strict-schemas is used.