You can run tdarr which is automated transcoding.
I think you're probably better off using something that's build for media servers. One really nice feature is adding more processing nodes to make things go faster, like a gaming PC while not playing anything. I don't think Handbrake can do that by itself.
I just finished setting up transcoding for my media library, and the options I found were Tdarr, FileFlows and Unmanic. They all use ffmpeg and/or Handbrake under the hood, so it kinda comes down to preference. I went with FileFlows because it seemed the most intuitive to me, and it can also process other media like photos, music, audiobooks and ebooks.
I was going to suggest there should be a way to run handbrake locally while pointing its under-the-hood functions to handbrake-cli (also, yes, there's handbrake-cli) hosted on your server, but I found this instead:
https://medium.com/@joshuaavalon/encode-video-with-handbrake-on-server-17b6127f6ac7
godsspeed, OP
In case your Lenny client concatenates the dot to the link like mine: https://medium.com/@joshuaavalon/encode-video-with-handbrake-on-server-17b6127f6ac7
ffmpeg
Tdarr is the way to go
Container should have negligible overhead, the main problem you're going to see is where the in/out files are located and shared. Another plus there for docker, can map that volume to anywhere.
If you need a GUI, then handbrake with a web version sounds great, when I did it years ago they didn't have it.
Since then, I've learned ffmpeg and use that regularly and can schedule jobs well now. Definitely more advanced, but more built for server applications.
What are you using it for
Not really any performance impact from using it in docker.
But you could also use ffmpeg as that's what handbrake uses under the hood IIRC.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!