dockprom VS flood

This guide before was just just kinda streamlined version of of the great stefanprodan/dockprom.

Dockprom is a solid starting point. It gives the essentials and you can tweak it to your liking. For example I forgo Alertmanager (for now) but have added more exporters, data sources, etc.

For tracking stats - Grafana, paired with appropriate backends. Dockprom is a nice starting point as it comes with most things preconfigured. You just need to tweak them accordingly.

i used Dockprom (https://github.com/stefanprodan/dockprom) at one point, it looks and works well however I found the CPU usage at the time higher than it should be. Your CPU would handle it easily, but it was still causing 10% CPU usage which i didn't like. I don't think this is a widespread common issue it's a very popular project but just a heads up to keep an eye on CPU if you decide to test it out.

Take a look at https://github.com/stefanprodan/dockprom as a way to work with Docker, docker compose, grafana, prometheus and more.

https://github.com/stefanprodan/dockprom Read the YML and remove what you aren’t using.

If you run plex in a docker container I highly recommend this grafana dashboard setup: https://github.com/stefanprodan/dockprom

Something like dockerprom can do that for you :) https://github.com/stefanprodan/dockprom

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Only one that I'm aware of is Flood: https://github.com/jesec/flood

If you haven't seen the https://flood.js.org project before. It has subjectively a nicer ui and works with qbittorent.

You can install alternate web UIs very easy. I’m a big fan of Flood, which is mobile friendly: https://flood.js.org/

One note: I lean heavily on an API to manage it so I'd love to continue using flood, I tested qbittorrent with it briefly and it didn't go well.

You mean a torrent client? I’m using rTorrent with Flood (the new jesec fork that’s actually active) and it works brilliantly on mobile

https://flood.js.org/ ?

If it's just the web ui you're worried about perhaps look into installing Flood & see if it helps? It's going to be a better web ui overall. (I've never needed to use it personally but it's been recommended in the pat)

qbitorrent-nox with flood-ui

Impressive. But I dont get why they would rebuild the web client when there are existing options like: https://github.com/jesec/flood