Formerly /u/neoKushan on reddit

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

help-circle




  • The problem is that your stance is needlessly binary. Just because they were intended to “save the auto industry” doesn’t mean that they’re not also better for the environment.

    The narrative that the manufacturing of EV’s is just as bad as the pollution from ICE vehicles has long been debunked and even if you’re charging from home via the grid, that doesn’t mean it’s environmentally bad, the push towards renewable energy production is ongoing.

    The US is vastly behind the times but that’s not the fault of EVs. Take the UK for example, which is producing more and more green energy. It stopped burning coal years ago and regularly runs almost entirely on pure renewables. That means EV’s charging there are regularly being charged from renewables, even when pulling from the grid.


  • Kushan@lemmy.worldtoSelfhosted@lemmy.worldIs Plex really Self Hosting?
    link
    fedilink
    English
    arrow-up
    102
    arrow-down
    2
    ·
    17 days ago

    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.









  • Kushan@lemmy.worldtoSelfhosted@lemmy.worldDocker is hard work
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    2 months ago

    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.






  • It was a couple of weeks ago for me but I managed to get my docker compose script for all my infrastructure cleaned up and all versions of containers are now pinned.

    I have renovate set up to open PR’s when a new version is available so I can handle updates by just accepting the PR and it’s automatically deployed to my server.

    Nice and easy to keep apps up to date without them randomly breaking because I didn’t know if a breaking change when blindly pulling from latest.