Skip to main content

Demo Environment

Use this for internal demos where reliability and clarity matter more than full production fidelity.

Practical demo shape​

  • one deterministic config file
  • one operator driving service actions
  • one read-only audience viewing logs/state
  1. Keep only services required for the storyline.
  2. Add readiness checks on user-visible endpoints.
  3. Pre-warm dependencies before audience joins.
  4. Keep fallback commands ready for known failure points.

Example:

flowlayer-server -c ./flowlayer.demo.jsonc -s 127.0.0.1:6999 -token demo-token

During live demo​

  • avoid broad stop_all unless planned
  • use targeted restart for recoverable failures
  • narrate states from TUI (starting, running, ready, failed)

Post-demo​

  • collect key logs with explicit limit
  • store incident notes alongside config revision
  • prune temporary demo-only overrides from main config

See Understanding Service States and Reading Startup Waves.