33 lines
1.2 KiB
ReStructuredText
33 lines
1.2 KiB
ReStructuredText
Configuration
|
|
=============
|
|
|
|
The runtime helper reads configuration from .env at the package root by
|
|
default. Set ENV_FILE to select another file:
|
|
|
|
.. code-block:: console
|
|
|
|
ENV_FILE=/path/to/.env bash scripts/runtime/run_validator.sh
|
|
|
|
The Compose deployment has a separate deployment configuration file at
|
|
deploy/docker/.env. It supplies Compose variables as well as environment
|
|
variables for the runtime wrapper. The helper recognizes controls for run
|
|
retention, RIR selection, TAL input, resource-validation mode, storage
|
|
locations, mirror reuse, retry intervals, and progress logging. Inspect
|
|
deploy/docker/.env.example and the helper's usage output before changing
|
|
production-like settings.
|
|
|
|
Runtime state
|
|
-------------
|
|
|
|
By default, state, run reports, logs, and temporary files are placed below
|
|
the package root. Set RUN_ROOT to move them elsewhere. These locations are
|
|
runtime data, not source inputs, and should be retained or removed according
|
|
to the operator's own recovery policy.
|
|
|
|
Network safety
|
|
--------------
|
|
|
|
Use bounded timeouts and explicit network access policies in automation.
|
|
Publication points are untrusted network inputs, so test configuration
|
|
changes against known fixtures before applying them to a long-running service.
|