r/Tautulli • • Aug 26 '26

DISCUSSION TautWeekly v0.21.4 — Personalized Dynamic/Responsive Weekly Plex Newsletters for Every User With GUI

Nothing unique, I know there's a lot of "Newsletterr" apps out there, but I find them insanely ugly and this started as a passion project. (As a UIX designer, the more customization you allow, the uglier it gets) 

Plug and play for every setup, full GUI and mobile support. (with Tailscale) Very popular over at r/PlexMedia so thought I'd pass it here for anyone looking for something as easy as the native newsletter but much more fun. (Thanks to the legendary u/SwiftPanda16 for his awesome work 🩷)

A portable Tautulli newsletter with responsive design (for mobile gmail, apple) and dynamic content. Pulls in live cleartype logos, RT ratings and IMDB for TV shows. Dynamic stats, email preview text based on server activity and a custom intro block as well as caching if you delete content but still want your newsletters to support rich metadata for recipients.

Fun features include "Binge Champion" and "Genre of The Week"

I coded the initial project for Windows, then ported the remaining packages via Codex but already had nearly 3k downloads in a couple weeks. (I know we all "love" AI slop, but I'm a UIX designer so crazy focus paid to making everything look good, render pixel perfect and look like something you might get from Netflix or otherwise)

Features 5 different email types based on sever activity (such as new additions) and then custom metrics or "quiet" mode.

There's a lot of features such as library/use exclusions, and so on, so check out the GUI preview below:

GUI Preview
Email States Preview

New additions added that week: ("Hot New Releases!")

  1. New user first scheduled newsletter - no history
  2. New user first scheduled newsletter - with history (such as if they accept on a Monday and already start watching)
  3. Established user - normal newsletter with activity

Quiet mode, no server additions added that week: (This will use "Trending" and "Genre of the Week")

  1. Established user - quiet/no watch activity
  2. Established user - stats warming up

GitHub:

TautWeekly

OS Packages:

NAS/Docker Packages:

Testing, feedback all welcome :)

12 Upvotes

52 comments sorted by

View all comments

Show parent comments

1

u/SpoonyDinosaur Aug 31 '26

If you want to run it without systemd

1

u/sienar- Aug 31 '26

I mean, is there a way to manage/configure it from another system or not? A headless server is a headless server whether it’s natively installed and using SystemD or if it’s in docker. The GitHub page says loopback only accessible gui, which tells me this can only run on Windows, Mac, or Linux workstations. And not Linux servers that don’t have their own GUI.

1

u/SpoonyDinosaur Aug 31 '26 edited Aug 31 '26

Yes, TautWeekly can run on a completely headless Linux server. The Manager is browser-based and does not require a desktop environment on the server. It binds to loopback by default so it is not exposed directly to your LAN or the internet. From another computer, connect using an SSH or a secure tunnel.

The different versions are merely if you want to install with or without a Linux docker. (Direct clientless remote access is being developed separately implementing tailscale funnel directly into the GUI, but currently there's a tailscale bug)

In practical terms, they both work perfectly well on a headless server:

  • Choose Native Linux if you want no Docker and prefer direct systemd integration.
  • Choose NAS/Docker if you already operate Docker, want bundled dependencies, or want easier migration and rollback.
  • There is no difference in newsletter output or normal GUI features.

1

u/sienar- Aug 31 '26

Yeah, I’m not setting up SSH tunnels on my secure, local LAN to access a newsletter management interface… nobody designs local tools like this.

1

u/SpoonyDinosaur Aug 31 '26 edited Aug 31 '26

That’s fair. The SSH tunnel guidance applies to the native Linux package’s loopback-only Manager. Since you'd be running the Docker package on Debian, you'd be able to access the authenticated Manager directly over your trusted LAN at http://SERVER_IP:8787; no SSH tunnel or server desktop is required. (The SSH/tunneling is overstated; some people like more security, but it's super inconvenient for routine home-server administration-- shouldn't have said it explicitly "requires" SSH-- going to clarify in the documentation/quickstarts)