Advanced Configuration

This page is for self-hosted RealTimeX administrators who need deployment-level behavior that is not handled through the normal in-app settings screens.

Most day-to-day setup should still happen in the app:

• Settings > AI Providers
• Settings > Agents
• Settings > Chat
• Settings > Privacy
• workspace-specific settings

Use this page only when you are managing the environment that starts the RealTimeX services.

Before you change anything

• Edit the environment source that starts your deployment, not random files inside the app bundle.
• Restart the affected RealTimeX service after changing an environment variable.
• If the setting affects media import or scraping, restart the related collector process too.
• Treat these flags as instance-wide behavior, not workspace-level preferences.

Disable View Chat History

Use DISABLE_VIEW_CHAT_HISTORY when the instance administrator wants chat history hidden from the normal UI and frontend history endpoints.

When this flag is present:

• chat histories are blocked from the regular frontend history views
• workspace and embed chat history review is blocked in those interfaces
• export and delete actions tied to that history UI are also affected
• the underlying chat data is not deleted

This is a visibility restriction, not a data-erasure setting.

Enable

DISABLE_VIEW_CHAT_HISTORY=1

Disable

Remove or comment out the variable.

Simple SSO Passthrough

Use SIMPLE_SSO_ENABLED when another system already authenticates your users and you want that system to hand them into RealTimeX without a full OAuth integration.

This is best for internal or tightly controlled deployments where:

• your users already exist in RealTimeX
• multi-user mode is enabled
• an admin can issue API-backed login links for those users

Enable

SIMPLE_SSO_ENABLED=1

How it works

After enabling it, an API client can issue a short-lived, single-use login token for a known RealTimeX user through:

/v1/users/{id}/issue-auth-token

The response includes a login path such as:

/sso/simple?token=...

That link can also include redirectTo=... when you want the user to land on a specific workspace or route after login.

Disable the normal login page

If the external system should be the only login path, also set:

SIMPLE_SSO_ENABLED=1
SIMPLE_SSO_NO_LOGIN=1

When both flags are present in multi-user mode:

• credential-based login is blocked
• invitation-based self-serve account creation is blocked

Disable

Remove or comment out SIMPLE_SSO_ENABLED. Remove SIMPLE_SSO_NO_LOGIN as well if you set it.

Community Hub Bundle Downloads

Use COMMUNITY_HUB_BUNDLE_DOWNLOADS_ENABLED when you want a self-hosted instance to download bundle-based items from the RealTimeX Hub.

This is intentionally restricted because some imported items can contain executable or automation-related behavior.

Safer mode

COMMUNITY_HUB_BUNDLE_DOWNLOADS_ENABLED=1

This allows:

• verified public items
• private items intended for your team

Fully permissive mode

COMMUNITY_HUB_BUNDLE_DOWNLOADS_ENABLED=allow_all

This also allows unverified public items. Only use this if you understand the risk of importing untrusted bundles into your own environment.

Disable

Remove or comment out the variable.

Local IP Address Scraping

Use COLLECTOR_ALLOW_ANY_IP when you intentionally want the collector to reach local or private IP targets during scraping or URL-based collection.

This is useful only for special deployments, for example:

• internal dashboards
• intranet tools
• services bound to private network ranges

Enable

COLLECTOR_ALLOW_ANY_IP="true"

The value must be the string "true".

Disable

Remove the variable or set it to another value.

Generic OpenAI Streaming Compatibility

Use GENERIC_OPENAI_STREAMING_DISABLED when you configured the Generic OpenAI provider against an endpoint that does not support streaming responses correctly.

This affects only the Generic OpenAI provider path, not other LLM providers.

Enable

GENERIC_OPENAI_STREAMING_DISABLED="true"

Disable

Remove the variable or set it to another value.

OCR Target Languages

Use TARGET_OCR_LANG when your deployment regularly parses images or PDFs that are not primarily English.

This controls the OCR language list used during text extraction for supported parsing flows.

Example

TARGET_OCR_LANG=eng,deu,spa,fra

Use Tesseract-compatible language codes only. Unsupported codes are ignored.

When to change it

• change it when OCR quality is poor for your document languages
• leave it alone if your instance is mostly English-language

Meeting Minutes Media Import

Some Meeting Minutes imports depend on FFmpeg and long-media chunking behavior. These settings matter more on self-hosted deployments than on normal in-app usage.

FFmpeg and FFprobe overrides

If your deployment cannot find working media binaries automatically, you can point RealTimeX at specific local binaries:

REALTIMEX_FFMPEG_PATH=/absolute/path/to/ffmpeg
REALTIMEX_FFPROBE_PATH=/absolute/path/to/ffprobe

You can also override command names if they are available on your system path:

REALTIMEX_FFMPEG_COMMAND=ffmpeg
REALTIMEX_FFPROBE_COMMAND=ffprobe

Auto-download behavior

If you want RealTimeX to fetch supported FFmpeg binaries automatically where that runtime supports it:

REALTIMEX_FFMPEG_AUTO_DOWNLOAD=true

There are also checksum and verification-related overrides in the example env files for stricter deployments.

Media chunk overlap

For long Meeting Minutes media imports, you can tune overlap between transcription chunks:

MEETING_MINUTES_IMPORT_MEDIA_CHUNK_OVERLAP_SECONDS=8

Increase it only when you have a specific boundary-loss problem during long media transcription.

Where to look next

• Review server/.env.example for server-side deployment variables.
• Review collector/.env.example for collector-specific media and ingestion variables.
• Keep regular product setup in the in-app settings whenever possible.

Related guides

• API Access & Keys
• Chat Logs
• Meeting Minutes
• MCP Servers