Formerly /u/neoKushan on reddit

  • 0 Posts
  • 59 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle
  • It’s self hosting by the literal definition that you host the server yourself.

    That it’s closed source and sends all kinds of data to another server is an entirely separate (and valid) concern.

    As much as I agree with the concerns around Plex, I would rather we didn’t start gatekeeping the self hosting community with arbitrary requirements and grey lines around what is and isn’t “true self hosting” or whatever. I would far rather we inform people and let them make their own choices about what they want to host on their private devices and networks.


  • You’ve done the hard work building the compose file. Push that file to a private GitHub repository, set up renovate bot and it’ll create PR’s to update those containers on whatever cadence and rules you want (such as auto updating bug fixes from certain registries).

    Then you just need to set up SSH access to your VM running the containers and a simple GitHub action to push the updated compose file and run docker compose up. That’s what I do and it means updates are just a case of merging in a PR when it suits me.

    Also I would suggest ditching the VM and just running the docker commands directly on the TrueNAS host - far less overheads, one less OS to maintain and makes shares resources (like a GPU) easier to manage.

    You should look at restic or Kopia for backups, they are super efficient and encrypted. All my docker data is backed up hourly and thanks to the way out handles snapshots, I have backups going back literally years that don’t actually take up much space.




  • I generally agree with the sentiment but don’t pull by latest, or at the very least don’t expect every new version to work without issue.

    Most projects are very well behaved as you say but they still need to upgrade major versions now and again that contains breaking charges.

    I spebt an afternoon putting my compose files into git, setting up a simple CI pipeline and use renovate to automatically create PR’s when things update. Now all my services are pinned to specific versions and when there’s an update, I get a PR to make the change along with a nice change log telling me what’s actually changed.

    It’s a little more effort but things don’t suddenly break any more. Highly recommend this approach.







  • Start off simple, use something like uptime-kuma just to check your services are available - takes minutes to set up and can send you notifications when something goes down. It can plug into docker directly to check if a container is up, as well as perform HTTP checks that the service is responding, plus some other cool stuff.

    (Side note, I set up ntfy to handle notifications and it’s great! Another solid recommendation but you can use discord web hooks or whatever as well)

    The other options described here are good for gathering and visualising data, but it takes quite a bit to set them up and even more to configure the right kinds of alerts to notify you when something is wrong. A simple “is this docker container running” check or a “does this respond with a http 200” check gets you like 95% the way there.




  • This is a "slippery slope’ argument and thus a fallacy.

    Let users decide how they want to run their own stuff. Right now if you have Plex pass this isn’t an issue. If it becomes an issue, then you’re in the exact same position you’d be in today if you decided to move away from Plex now.

    I moved away from Plex years ago, but I don’t blame users for sticking with it, it still has a lot of advantages over jellyfin.

    EDIT: Y’all are trippin’ over yourselves to complain about what other people choose to deploy on their own hardware.




  • Kushan@lemmy.worldtoPrivacy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 months ago

    Please don’t tell me what I am focusing on, when I haven’t even said it

    I literally quoted you, so don’t try playing the “I never actually said that” card.

    It’s ironic that you’re now complaining about context and strawmen when you yourself started it with the whole “anyone who wants to know who you are…” argument. This mysterious “anyone” is the ultimate strawman because they’re anonymous and all encompassing. Meanwhile, you have zero idea what anyone wants from their VPN’s so you’re making the broad, sweeping statements while lacking any context yourself.


  • Kushan@lemmy.worldtoPrivacy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 months ago

    A dumb take is, to pay for something you might get nothing from

    And which VPN provider is it you’re getting “nothing” from? There seems to be a budding market for VPN’s out there, lots of people are paying for them and continue to do so, why do you think that is? Because the whole world is stupid and it’s a pointless waste of money? Or because they are actually in fact getting some kind of use from them?

    VPN’s have a myriad of uses, you’re focusing on some ambiguous nation-state attacker tracking you down for whatever reason. Meanwhile, quite a lot of users would just like to watch porn without having to submit ID. I’d say they’re getting plenty of use out of their VPN for that.