Skip to main content

Crate rivetkit_engine_process

Crate rivetkit_engine_process 

Source

Structs§

EngineProcessManager
Manages the rivet-engine subprocess.
EngineResolverConfig
EngineRuntimeStamp
Effective runtime parameters of a spawned engine, stamped to disk so a later process that reattaches can tell how the running engine is configured without probing it over the network.

Enums§

EngineProcessError
EngineStartup
How start_or_reuse satisfied the request.
ResolvedEngine

Functions§

engine_data_path
Path to the local engine’s Depot data under the shared storage root. It holds the log shard and the object store, and is kept apart from the db directory older engines used.
engine_env
Computes the environment variables that configure a rivet-engine process for the given endpoint. The engine requires the log directory to exist; see engine_log_directory.
engine_log_directory
The local engine’s log shard directory, which must exist before the engine starts. The engine creates its object store directory itself.
resolve_engine_binary
resolve_engine_binary_path
Resolves the engine binary path without probing for an already-running engine.