Install and administration
The install page gets one server running in about ten minutes. These pages cover everything after that, from the master key to a second server.
One Linux server, Docker and about ten minutes, with every command on one page.
System requirementsLinux and Docker on x86-64, 32 GB of memory recommended, 100 GB of disk, and what changes on more than one server.
ConfigurationThe one setting you fill in, the master key, the admin account, and which profile runs what.
First sign-in and HTTPSSecure the admin account, then serve HTTPS by putting a certificate in one folder.
Single sign-onOpenID Connect and LDAP or Active Directory sign-in, and turning local passwords off (Enterprise).
UpgradingThree steps, and why the compose file is pasted again every time.
BackupsWhere backups go, encrypted or portable bundles, and what to copy off the server.
Scaling outMore servers on one PostgreSQL, shared file storage, and tags that decide which server runs what.
Disk spaceThe three volumes, why scratch grows during big runs, and moving it to its own disk.
LogsPlain-text logs, shipping them to your collector, and the audit feed for a SIEM.
Everyday commandsStart, stop, restart and follow the logs, and the one command that deletes data.
TroubleshootingWhat each startup refusal and common message means, and the fix.
Before you run a command
Every command on these pages runs on the server, in the folder holding compose.yaml (the install page creates it at ~/trinium). The commands are shown without sudo. Put it in front of docker, as the install page does, unless your account is in the docker group.
Where these pages come from
They are Trinium's advanced install guide, published section by section. Each page names the Trinium release it describes.