mirror of
https://github.com/4gray/iptvnator.git
synced 2026-10-16 06:06:18 -08:00
4grayandClaude Fable 5.1
b64b766f0a
* docs(website): self-hosting guide for server storage and a current Docker page The Docker download page still said that every browser keeps its own sources and that the container holds no state, which stopped being true when server storage landed (#1903). It now describes the shared library on the volume, lists IPTVNATOR_STORAGE, IPTVNATOR_DATA_DIR and IPTVNATOR_ACCESS_TOKEN, shows the volume in the compose snippet and points at a new step-by-step guide. The guide covers a NAS deployment with Docker Compose: the compose file, the first start, a second device and the browser-data move, the access token, HTTPS behind a reverse proxy, where the database lives and how to back it up, updating, NAS notes and troubleshooting. Its two screenshots were captured from the published image on a fresh volume with the project's mock providers. The comparison page's data FAQ and the guides hub list the guide, and the docker README links to it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(website): certificate prerequisites and a safe host backup in the guide Review round 1 (Codex, Greptile): the Caddy example used a name no public authority can certify, so the HTTPS step now explains the two workable setups, a name you own with a Let's Encrypt certificate or a LAN name with Caddy's internal authority trusted on each device, and shows both. The host-side backup no longer suggests copying the database and its journal from a running container; the docker README says the same. The token step loses literal backticks that the step rail rendered as text. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(website): a restored backup keeps its sign-ins Review round 2 (Greptile): the instance id lives in the database, so a restored copy of the same database keeps every browser signed in. The guide now says so in the restore paragraph and in troubleshooting, and reserves the new-server flow for a database with another identity. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(website): two libraries need two container names Review round 3 (Codex): the FAQ on separate libraries sent readers to copy the compose file, whose fixed container_name would make the second container fail to start. The answer now lists the container name among the values that must differ. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(website): say when another device's changes arrive Review round 4 (Greptile): an open page re-reads the synced user data when its tab comes back to the front or on a reload, not when a list inside it is opened again. The guide's sentence on propagation says so. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs(website): keep the self-hosting guide a draft until the 0.25 release The post stays out of the published site for now. The Docker page links it only when the post is built (published, or drafts included), the website test checks it in the drafts-included run like the other draft guides, and the docker README link waits for the publication. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
