From d1974f10c5e4d456004d805254a66dc85f9ffebc Mon Sep 17 00:00:00 2001 From: Pauljd Date: Thu, 12 Nov 2026 15:02:47 +0000 Subject: [PATCH] docs: the VPS's required settings, permission vs capacity, first measurements Co-Authored-By: Claude Opus 5.5 --- docs/VPS-DEPLOYMENT.md | 52 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 docs/VPS-DEPLOYMENT.md diff --git a/docs/VPS-DEPLOYMENT.md b/docs/VPS-DEPLOYMENT.md new file mode 100644 index 00000000..45e38cd6 --- /dev/null +++ b/docs/VPS-DEPLOYMENT.md @@ -0,0 +1,52 @@ +# Orbit's own Emby VPS + +Paul's server from 12 November 2026: a provider VPS (2 cores, 12 GB, Finland) running its own Emby 4.10, pointed at the +provider's shared library storage. About 94,700 films, 20,600 series and 525,000 episodes. Address and login are in the +provider's portal; the API key for tests is in `~/Documents/OrbitTV/vps/.token`, never in the repo. + +## Settings that must stay off + +These are the provider's rules. Breaking them gets the service banned. Check them after every redeploy, rebuild or Emby +update with `python3 -I ~/Documents/OrbitTV/vps-test/check-settings.py` (read-only). + +| Setting | Where | Must be | +| --- | --- | --- | +| Real-time monitoring | Each library's options | Off, on all 14 libraries | +| Chapter image extraction | Each library's options | Off | +| Video preview thumbnail extraction | Scheduled Tasks | No trigger | +| Detect Episode Intros | Scheduled Tasks (hidden; only the API can see it) | No trigger | +| Live TV | Live TV settings | No tuner, no guide | +| Transcoding | Not licensed | Orbit only direct-plays | + +A redeploy brings back the provider's defaults, so all of these need setting again. "Recreate (keep data)" should keep them, +but check anyway. + +## Server permission and server capacity + +Orbit keeps two ideas apart: + +- **Permission:** what the server's owner allows. A server Orbit doesn't know is treated as shared: a quiet first week, + background work capped at 100 an hour, then 200, and everything under 400 an hour in total. Only the owner can mark a + server as their own (`--es orbit_own_server on` today; a setting later), which lifts the quiet week. A fast answer is never + taken as permission: a big shared server can answer in 20 ms with hundreds of people on it. +- **Capacity:** what the server can take. Orbit backs off by itself when answers slow or fail (the gap between background + requests doubles, up to a minute), whatever the permission. + +Permission always wins. Capacity can only make Orbit gentler than permission allows, never busier. + +## Measurements + +| When | What | Result | +| --- | --- | --- | +| 12 Nov 2026, during the first scan | Episode lists | about 0.3 s | +| 12 Nov 2026, during the first scan | Title searches | 0.2 to 0.5 s | +| 12 Nov 2026, during the first scan | Library pages of 200 | about 1.2 s | +| 12 Nov 2026, during the first scan | Collections list | over 30 s (timed out twice) | + +Measure again after the scan. Numbers taken while Emby is indexing show its indexing load, not its normal running. + +## First run on a big library + +Orbit doesn't wait for the library to be read before you can watch. Switching a channel on searches for that channel's +titles directly (about 50 to 100 requests at one a second), so the first channel plays within a minute or two. The full +library read, the collections and the Director's Chair fill in afterwards, in the background, within the limits above.