-
Notifications
You must be signed in to change notification settings - Fork 0
Configuration.notes
# /etc/selenium-flow/config.yaml
session:
ttl: 86400
redis:
host: redis.data
db: 2export CONFIG_FILE=/etc/selenium-flow/config.yaml
export GRID_URL=http://selenium-hub:4444
selenium-flow --log-level DEBUGThe Settings tab of the admin UI shows every value and where it came from.
session.page_load_timeout: with no bound, one hung page holds a Grid slot
until the Grid reaps it.
An environment variable the server does not know is ignored: Kubernetes
injects <SERVICE>_PORT variables into every pod. A key the file does not
know stops the boot, because it is a typo.
The exception: a Kubernetes Service literally named redis injects
REDIS_PORT=tcp://…, which is a known leaf and stops the boot on a value
that was never meant as one. Hence enableServiceLinks: false on the pod.
secrets.dirs splits like PATH, on the OS path separator (:). A boolean
setting accepts true/false, 1/0, yes/no and on/off.
The file's secrets.entries section defines secrets. See Secrets.
The action pages are generated from openapi.yaml, which is itself generated from the live MCP tool schemas — so they describe the server that shipped, not the one someone remembered. Prose belongs in wiki-notes/<tool>.md in the repo.
selenium-flow · MIT
Start here
Guides
Lifecycle
Going places
Doing things
Getting things out