Skip to content

Runtime Config Reference

This page summarizes the most visible runtime configuration entrypoints for the server binary.

Runtime Config Inputs

flowchart LR
    Flags[Startup flags] --> Runtime[Server runtime]
    Files[Config file] --> Runtime
    Env[Environment variables] --> Runtime

This input diagram shows the three main ways runtime configuration reaches the server. It is meant to support fast lookup, not to replace the deeper operational guidance in the operations section.

Visible Server Flags

flowchart TD
    Server[bijux-atlas-server] --> Config[--config]
    Server --> Bind[--bind]
    Server --> Store[--store-root]
    Server --> Cache[--cache-root]
    Server --> Effective[--print-effective-config]
    Server --> Validate[--validate-config]

This flag map calls out the highest-signal server startup options so readers can identify the exact entrypoint they need without reading full help output first.

Key Flags

  • --config: explicit config file input
  • --bind: network bind address
  • --store-root: serving store root
  • --cache-root: runtime cache root
  • --print-effective-config: inspect resolved runtime config
  • --validate-config: validate runtime config without normal startup

Key Rule

--store-root should point at a serving store with published artifacts and catalog state, not at an ingest build root.

Purpose

This page is the lookup reference for runtime config reference. Use it when you need the current checked-in surface quickly and without extra narrative.

Stability

This page is a checked-in reference surface. Keep it synchronized with the repository state and generated evidence it summarizes.