94
submitted 2 months ago by eric@lemmy.ca to c/selfhosted@lemmy.world

cross-posted from: https://lemmy.ca/post/30126699

I created this guide on how to install Jellyfin as a Podman Quadlet on your server. Enjoy.

you are viewing a single comment's thread
view the rest of the comments
[-] lime@feddit.nu 9 points 2 months ago

this guide, and the previous one, have a lot of weird superfluous steps. like, why use a command that includes nvim and then ask people to change it instead of just saying "edit the file"? why symlink systemd stuff to your own home directory?

the info is good, but having to separate the actually useful stuff from things that are specific to your config makes it less useful.

[-] eric@lemmy.ca 4 points 2 months ago

I'm still learning how to write good posts. I'll this into consideration for the next one.

[-] lime@feddit.nu 4 points 2 months ago

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.

[-] eric@lemmy.ca 3 points 2 months ago

That's a good tip. Thanks. I think I might tweak the existing posts for readability.

[-] eric@lemmy.ca 1 points 2 months ago

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/

[-] lime@feddit.nu 1 points 2 months ago

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)

[-] eric@lemmy.ca 1 points 2 months ago

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.

[-] lime@feddit.nu 1 points 2 months ago

i'm glad you found it useful, best of luck :)

this post was submitted on 01 Oct 2024
94 points (93.5% liked)

Selfhosted

40696 readers
320 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS