Technical Configuration

Technical configuration reference

Audience: developers and advanced administrators. Baseline reviewed: 2026-10-29.

Configuration layers

Layer	Location/interface	Interpretation
Deployment configuration	videos/configuration.php, $global	Installation paths, URLs and private connection material; excluded from this documentation
Site configuration	AVideoConf, configurations	Site-wide persisted configuration
Plugin defaults	getEmptyDataObject()	Source-level construction of initial fields
Plugin saved settings	plugins.object_data through plugin accessors	Persisted values merged with defaults
Structured options	Objects containing fields such as type and value	UI definition plus selected value; not always a scalar
Per-user/job/provider state	Plugin data classes, preference/state files or provider API	Scoped operational data; not a site-wide default

How to trace a field

1. Record the exact interface label and internal field name.
2. Find the owning plugin in the technical plugin catalog.
3. Read its default construction and any addDataObjectHelper() description.
4. Search every consumer of that exact field in the relevant component, including the Encoder when appropriate.
5. Check saved values, structured selections, conditional overrides and enabled-state checks in the actual installation.
6. Confirm the output or state transition the setting controls.

Do not infer a universal default from a sample Docker configuration or another server's saved settings. A setting can exist while its feature is disabled or unavailable.

Important examples

• Encoder URL: identifies the Web Encoder used for queue/media utility requests. A Local Encoder browser page is not a replacement endpoint.
• Live URLs: RTMP ingest, HLS player URL, stats, control and remote recording transfer are separate addresses/contracts.
• Advanced FFmpeg options: current Streamer conversion code parses allowed options before execution. A stored text string is not necessarily interpolated directly into a shell command. Follow the actual conversion wrapper.
• TLS behavior: configured outbound-service verification is mediated by shouldVerifySSLCertificates() in relevant callers. Inspect the service-specific path and deployment policy instead of assuming all outgoing requests share one rule.
• Restricted advanced configuration: disableAdvancedConfigurations can prevent saves or affect selected runtime options. Read objects/dangerousConfigurations.php and the save/consumer path when this mode is involved.

Version and support boundaries

Names, defaults and consumers can evolve independently in separately distributed plugins. Each plugin page records the code-reported version and source revision. A configuration table is evidence from that source snapshot; it is not a claim that every older installation offers the same fields.

The basic hidden-configuration guide remains the user-facing entry point. Use this page when implementation tracing is required.