Skip to content

Environment variables

These names belong to the generated upper application. Elura itself does not read environment variables.

Secrets

VariableRequired byDescription
APP_TICKET_KEYGateway, monolithTicket signing/verification key; at least 32 bytes
APP_INTERNAL_TOKENSplit Gateway and WorldPrivate command authentication; at least 32 bytes and different from ticket key
APP_ADMIN_TOKENNon-loopback admin listenerBearer token for metrics/debug/admin; at least 32 bytes

Configuration paths

VariableDefault
APP_GATEWAY_CONFIGconfig/gateway.json
APP_WORLD_CONFIGconfig/world.json
APP_MONOLITH_CONFIGconfig/monolith.json

Listener overrides

VariableExample
APP_GATEWAY_ADDR0.0.0.0:17000
APP_GATEWAY_ADMIN_ADDR0.0.0.0:17001
APP_WORLD_LISTEN0.0.0.0:18000
APP_WORLD_ADMIN_ADDR0.0.0.0:18001
APP_INSTANCE_IDPod name or stable process identifier

Deployment and application examples

VariablePurpose
ELURA_IMAGEDocker Compose image override; defaults to elura-game:dev
DATABASE_URLReserved example for application persistence
ACCOUNT_SERVICE_URLReserved example for an account service
CHARACTER_SERVICE_URLReserved example for a character service
APP_REDIS_CLUSTER_NODESExample application-owned Redis seed list

The generated binaries do not read the reserved business/adapter examples until the application adds them to AppConfig.

Shell usage

bash
set -a
. config/elura.env
set +a
cargo run --bin gateway

In production, inject secrets using the platform’s secret mechanism. Avoid putting values directly in command arguments, images, ConfigMaps, or source control.

Released under the MIT License.