# uo-link sidecar configuration — example.
#
# The sidecar reads `sidecar.toml` (override the path with --config or $UOLINK_CONFIG).
# If that file is absent on first run, one is generated automatically with a random
# auth_token, so you normally do not create this by hand — just start the sidecar and edit
# the file it writes. Nothing here is compiled into the binary.
#
# Environment variables override the file:
#   UOLINK_SHARD_BIND, UOLINK_WEB_BIND, UOLINK_WEB_TOKEN, UOLINK_DB_PATH
#
# Read the resolved settings back without starting the sidecar (JSON, includes the token):
#   uo-link-sidecar --print-config --config /etc/runicgateway/sidecar.toml

[shard]
# Loopback address the shard dials out to. Keep this on localhost — the game must not
# be reachable from anywhere else.
bind = "127.0.0.1:7788"

[web]
# Address the website connects to (WebSocket + REST).
#   127.0.0.1:8080  -> same host only
#   0.0.0.0:8080    -> accept remote clients (then auth_token is mandatory)
bind = "127.0.0.1:8080"

# Shared secret the website must present on every request:
#   REST:      Authorization: Bearer <token>     (or  X-Api-Key: <token>)
#   WebSocket: add  ?token=<token>  to the connect URL
# Authentication is ALWAYS on. If this is left blank, the sidecar generates a token
# here on startup and logs it. Rotate by changing this value and restarting.
auth_token = "replace-with-a-long-random-secret"

[store]
# A RELATIVE path resolves against the directory holding this file, not the working
# directory of the process — so a service pinned to /etc/runicgateway/sidecar.toml keeps
# its database beside its config no matter what CWD the service manager picked. Give an
# absolute path (or set UOLINK_DB_PATH) to put the data somewhere else, e.g.
# /var/lib/runicgateway/uo-link.db or C:\ProgramData\RunicGateway\uo-link.db.
path = "uo-link.db"