Deploying a TiLive Recorder on a VPS
Before pointing a domain at the service, the VPS needs a clean runtime: recorder process, database path, web build, admin secret, FFmpeg, Node runtime, and persistent logs.
Install the media dependencies
FFmpeg and ffprobe must be available in PATH. Node is also required for the native RTC recorder scripts.
The Agora and TRTC recorder scripts should be installed with their own package dependencies before the bot starts.
Keep one database path
The bot writes to SQLite and the web/admin apps read the same database. Configure RECORDER_DB_PATH or DATABASE_PATH consistently.
If the site points at a different database, the public pages will look stale even while the bot records correctly.
Run processes separately
Use a process manager for the bot and the two Next apps. Restarting the web app should not kill an active recording.
Keep recordings on a disk with enough temporary space because uploads happen after the live finishes.
Before DNS, run bot, web, and admin locally against the same SQLite file and verify a recording appears on the site.
Open @tiliverec_bot