Dialectic Linux Setup Guide

DialecticServer runs inside the Linux-based DwemerDistro environment while Fallout and the xNVSE plugin remain on the Windows gaming PC.

The supported one-click installation is DwemerDistro through WSL on Windows. A native Linux host is an advanced manual deployment and is not managed by the Windows launcher.

Native Linux Requirements

A manual native deployment needs a web server with PHP, PostgreSQL, required PHP extensions, write access to DialecticServer runtime folders, and any selected LLM, TTS, or STT services.

Use the tracked DialecticServer release tree and keep the web path as:

/var/www/html/DialecticServer

The default database is named dialectic. Apply the baseline and database update chain before opening the UI.

Web Access

Expose the Apache port to the local network and verify the UI from the gaming PC:

http://<LINUX_SERVER_IP>:8088/DialecticServer/ui/index.php

The exact external port can differ in a manual deployment. Use the port actually mapped to the DialecticServer Apache listener.

Point The Fallout Client At Linux

Set the server address in the gaming PC's separate dialectic_custom.ini:

[Server]
Host=192.168.1.101
Port=8088
Path=DialecticServer/main.php

Keep the Windows Fallout installation, xNVSE plugin, ESP, MCM, and custom INI on the gaming PC.

Local AI Services

Install only the services used by your selected connectors. GPU-backed components require a working Linux NVIDIA runtime and access to the GPU. CPU-compatible services can run without it at lower performance.

Test every connector from DialecticServer before testing it through Fallout.

Permissions And Persistence

The Apache/PHP user must be able to write DialecticServer's configuration, cache, temporary job, upload, and log locations. PostgreSQL data and server configuration must live on persistent storage.

Do not expose PostgreSQL or AI service ports to the public internet. Keep the setup on a trusted LAN or place it behind appropriate authentication and firewall rules.

Updates

DwemerDistro installations should use the launcher update flow. Native Linux administrators must pull the intended DialecticServer release, preserve runtime configuration, apply database updates, and restart the relevant workers and web services manually.