Jellyfin is everyone’s favourite open-source multimedia player. This guide goes over how to install it as a Podman Quadlet. This assumes you already have Podman setup for Quadlets. Follow this guide to setup Podman for Quadlets.
Create the container First, create and edit sudo nvim ~/containers/jellyfin.container, if you don’t use Neovim, replace nvim with whichever text editor you prefer.
Paste the follwing. Replace {USER} with your user, {PUID} with the value of id {USER} -u, {PGID} with the value of id {USER} -g, and change your time zone accordingly.
your writing overall is good! it’s just a matter of information priority.
here’s a tip, dunno how applicable it is but i use it when writing technical documentation:
for each step, explain to yourself why you’re doing it the way you are. if it turns out you caused the step to be needed, rather than it being required, you probably need to rethink, or at least add the explanation to the text.
this is more focused for sure, but it lacks the enthusiasm of the original. if i was trying to do this for work, i would appreciate how quickly it gets to the point. however, it no longer reads like this is something you’re interested in. it reads a bit wooden. i get that would happen after you’ve been told to correct your style though.
to be clear, the original article doesn’t need to be rewritten. for the future though, when you want to tell the story of how you got something working, include your reasons for doing something a certain way. if you need a self-inflicted complication, that’s not really a part of it (unless it’s funny)
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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).
your writing overall is good! it’s just a matter of information priority.
here’s a tip, dunno how applicable it is but i use it when writing technical documentation:
for each step, explain to yourself why you’re doing it the way you are. if it turns out you caused the step to be needed, rather than it being required, you probably need to rethink, or at least add the explanation to the text.
That’s a good tip. Thanks. I think I might tweak the existing posts for readability.
I rewrote my original quadlet article, can you have a look and let me know what you think? https://ericthomas.ca/posts/setting-up-podman-quadlets/
this is more focused for sure, but it lacks the enthusiasm of the original. if i was trying to do this for work, i would appreciate how quickly it gets to the point. however, it no longer reads like this is something you’re interested in. it reads a bit wooden. i get that would happen after you’ve been told to correct your style though.
to be clear, the original article doesn’t need to be rewritten. for the future though, when you want to tell the story of how you got something working, include your reasons for doing something a certain way. if you need a self-inflicted complication, that’s not really a part of it (unless it’s funny)
I’m picking up what you’re throwing down. I’m writing one on qBittorrent and will take that into considering. Thanks for helping me.
i’m glad you found it useful, best of luck :)