Loading...
PyStator·Review live server runtime, edit admin config, and manage browser-local defaults for tools.·Browser values stay in localStorage; server values come from environment and pystator.cfg.
Read effective server values and, when signed in as Admin, edit values written to pystator.cfg. Environment variables still win over file settings.
Effective values from the API process: environment overrides pystator.cfg. Passwords are masked. Log in as Admin to edit the config file from this table.
These preferences are stored only in this browser and are used by UI requests and test tools. They do not change the running API or worker process.
Base URL this browser uses for API calls (stored in localStorage). Server default comes from PYSTATOR_API_URL / [api]. App: PyStator
Used by this browser for API requests outside same-origin development proxy mode.
Optional local test credentials for database, discovery, and DLQ tools. Use server runtime settings above for production process configuration.
Optional credentials stored in this browser for the Test connection action only. The running API uses PYSTATOR_DATABASE_URL (see server runtime above).
Enable database test fields
When off, values are kept in storage but hidden to reduce clutter.
Defaults stored in this browser for discovery tools and tests. Discovery backend type is inferred from the connection URL. The API worker uses [discovery] in pystator.cfg (editable in server runtime when you are an admin).
Inferred backend for this browser test: sqlite. Server runtime uses its fallback chain when no dedicated discovery URL is configured.
Shadow mode
Compare inferred candidates without enforcing them in production traffic.
Browser-only credentials for Test connection and Load statistics. Production worker settings use PYSTATOR_WORKER_DLQ_* (see server runtime).
Enable DLQ tool fields
Show connection fields, test, and statistics actions.
Browser-only editor behavior for FSM authoring. Server feature gates still decide what can execute.
Inline FSM code: actions use PYSTATOR_ALLOW_INLINE_CODE_ACTIONS, with optional imports controlled by PYSTATOR_ALLOW_INLINE_CODE_IMPORTS. Registry catalog source_code implementations use the separate PYSTATOR_ALLOW_CATALOG_CODE gate. The editor preference below is stored only in this browser.
Stored in localStorage as features.inlineCodeActionsEditor. It only controls whether the UI shows the inline Code action kind; server flags still decide whether execution, imports, and catalog source-code implementations are allowed.