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!
view the rest of the comments
The drive will be mounted by the host and you can use that to also decrypt it. This way Jellyfin in the docker container doesn’t know that the media is stored on an encrypted hard drive.
And if I make docker compose file for jellyfin and specify that path to encrypted hdd example( /media/user/sda1/jellyfin-media) will it be able to read that media?
I’m not 100% on the paths regarding the mounts and where the containing files are accessible, but it looks correct to at the moment. One way to test this is to check if the user you are using to run the Jellyfin container is able to access the files without additional input/steps.
If your user can access it, then Jellyfin will be able to do that as well as soon as you have mounted it in the container.