Ctrl K
ComunidadGuías…

deploy/systemd/predastore.env

Rama main · réplica de lectura del repositorio original.

Archivo original ↗Preguntar a KiBot
# Host-local settings for predastore.service, installed to
# /etc/predastore/predastore.env.
#
# The TOML at PREDA_CONFIG describes the cluster and is the same on every
# machine. This file is what only this machine knows. Everything except
# PREDA_HOST_ID is optional: an empty value falls through to the TOML.

# Which [[host]] in the TOML this process runs. Host 1 on two machines is a
# split cluster rather than a failure, so there is no safe default.
PREDA_HOST_ID=1

PREDA_CONFIG=/etc/predastore/predastore.toml

# The shipped TOML names these itself. Uncomment one to override it on this
# host alone, which is what a fleet running a single distributed TOML wants.
# PREDA_DATA_DIR=/var/lib/predastore
# PREDA_ENCRYPTION_KEY=/etc/predastore/master.key
# PREDA_TLS_CERT=/etc/predastore/server.pem
# PREDA_TLS_KEY=/etc/predastore/server.key

# Where raft and blob traffic listens, without a port. Set it to the private
# address on a multi-homed machine.
PREDA_BIND_ADDR=

# Where the S3 API listens, without a port. Pair a private PREDA_BIND_ADDR with
# 0.0.0.0 here to expose S3 alone.
PREDA_GATE_BIND_ADDR=

# /healthz and /readyz on PREDA_BIND_ADDR. Plain HTTP with no authentication,
# so keep it private. Zero defers to the TOML's admin_port.
PREDA_ADMIN_PORT=0

# debug, info, warn or error.
PREDA_LOG_LEVEL=warn