I kept seeing people juggle WhatsApp groups and spreadsheets to track what their friends want to watch, so I packaged Yamtrack as a one-click deploy template: https://github.com/INAPP-Mobile/yamtrack
Why it exists: every "what should we watch" conversation I observe ends up in chat history that scrolls away. Yamtrack gives a small self-hosted web app where users request movies and shows, vote, and see status — request → approved → available — without a third-party service holding that data.
One concrete detail: the template ships as a single Docker Compose file with the app and a lightweight SQLite database on a named volume, so the whole thing comes up with one command and survives container rebuilds. The tricky part was wiring the reverse proxy paths so the API and the web UI both resolve under one hostname — I ended up pinning the base path in the env template rather than trying to auto-detect it, because auto-detection broke the first time someone deployed under a subdirectory.
What it costs the operator: the database itself is nearly free, but poster and backdrop images are cached locally on first sync, and on a busy instance that cache grew to a few gigabytes within weeks. If you deploy it, mount the media cache on a volume you actually back up or prune — that's the one line item people forget to budget for.
